To answer the first question about 'domain decomposition'.. I don't
think it is something that 'most' or 'many' customers deal with.
Fair enough, but for HPC scientific applications it is definitely a
go-to functionality.
In that case, the usual method is 'build it yourself' or 'work with
others to build it in a 3rd party repository' like EPEL or similar ones.
Ok, so unless someone happens to pick it up, I guess I will have drop
binary builds for centos/redhat-9 for the time being. Possibly resort to
adding as an additional source for my own builds (when I find time).
The reasons for software not being in future RHEL is usually a split
thing.. There are customers who want a specific version in RHEL and
there are customers who do not unless because it is not the version they
wanted. That usually makes the choice toward not including something
because then no one is equally unhappy.
I understand. This was always a bit limited on RedHat with lock in to
some particular mpich or openmpi version. Better than debian/ubuntu,
where they only have a single MPI vendor, but definitely less than SUSE
with different MPI vendors/versions:
- libptscotch-gnu-mpich-hpc-6.1.0
- libptscotch-gnu-mvapich2-hpc-6.1.0
- libptscotch-gnu-openmpi2-hpc-6.1.0
- libptscotch-gnu-openmpi3-hpc-6.1.0
- libptscotch-gnu-openmpi4-hpc-6.1.0
In any case, thanks for the feedback. It is certainly useful to know the
root cause.
Cheers!
/mark
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
