[petsc-dev] [XSDK-DEV] PR20 - Vote next xSDK telecon (Oct 1st) (fwd)

Scott Kruger kruger at txcorp.com
Wed Sep 23 11:34:05 CDT 2020



Sorry if I'm missing something, but my take is that this is mostly going 
to affect  PETSc's spack package file which doesn't affect PETSc 
directly?    I'm struggling to see how this affects PETSc.

Scott



On 9/23/20 8:47 AM, Satish Balay via petsc-dev wrote:
> FYI - this policy change would affect petsc - and we [petsc] would have to vote on it..
>
> Too many issues here..
>
> Satish
>
> ---------- Forwarded message ----------
> Date: Fri, 18 Sep 2020 16:38:06 +0000
> From: "Hudson, Stephen Tobias P"
>      <00000d3a20d2ae38-dmarc-request at LISTSERV.LLNL.GOV>
> Reply-To: XSDK-DEV <XSDK-DEV at LISTSERV.LLNL.GOV>
> To: XSDK-DEV at LISTSERV.LLNL.GOV
> Subject: [XSDK-DEV] PR20 - Vote next xSDK telecon (Oct 1st)
>
> I want to aim to vote on PR20 at the next xSDK telecon (Oct 1st).
>
> PR20. https://github.com/xsdk-project/xsdk-community-policies/pull/20<https://github.com/xsdk-project/xsdk-community-policies/pull/20#issuecomment-682222452>
>
> Summary of changes:
>
> M1. Modified to base installation around Spack and includes compliance with the Spack variant guidelines.
>
> https://github.com/xsdk-project/xsdk-community-policies/blob/python-updates/installation_policies/xSDK_spack_variant_guidelines.md
>
> Note that these guidelines state that when configuration options exist for index size, precision, shared libraries and build_type then they should be reflected in Spack variants.
>
> The variant names/types listed are recommendations. Please think about whether you are happy with these variants for your code and make any comments either on the PR or on the xsdk slack page in the channel spack-variants-and-pr20 (https://app.slack.com/client/T01AWKXU6F5/C01B3T17P7E)
>
> The old installation polices have been combined into one document called pre_spack_install_policies.md<https://github.com/xsdk-project/xsdk-community-policies/blob/python-updates/installation_policies/pre_spack_install_policies.md> and are no longer part of M1.
>
> M16. The old M16 has been removed as this is incorporated into M1. A new M16 requires a Debug build option.
>
> If you have any questions or comments, and especially if I have overlooked any previous comments, please let me know either in PR or in the Slack channel referenced above.
>
>
> ########################################################################
>
> To unsubscribe from the XSDK-DEV list, click the following link:
> http://listserv.llnl.gov/SCRIPTS/wa.exe?SUBED1=XSDK-DEV&A=1

-- 
Tech-X Corporation               kruger at txcorp.com
5621 Arapahoe Ave, Suite A       Phone: (720) 974-1841
Boulder, CO 80303                Fax:   (303) 448-7756

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20200923/f480b5fa/attachment.html>


More information about the petsc-dev mailing list