https://bugzilla.suse.com/show_bug.cgi?id=1217751 Bug ID: 1217751 Summary: PETSc packaging is broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: badshah400@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- This is partly a rant, partly a cry for help brought about by trying to build a package that depends on petsc as it appears in Factory. TL;DR it is hell! The various flavours of the PETSc package install their headers and libraries to multiple non-standard locations (even after accounting for mpi paths). For example: * petsc-serial - Headers are in the `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt/include/` dir, they should be somewhere in `/usr/include` - Shared lib is in `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt/lib/`; should be in `/usr/lib64/petsc` at worst. - Pkgconfig file is in `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt/lib/pkgconfig/` where pkgconfig does not even look. Not surprisingly, installing petsc-devel and doing `pkgconfig --libs petsc` does not work. Side note: there is also a bonus 0 byte PETSc.pc file in the same dir. `petsc.pc` should be installed to `/usr/lib64/pkgconfig` - There is a supposedly-arch independent `share` dir in `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt` * petsc-openmpi4-devel (and other mpi/hpc flavours I have not dared to look into) - Headers: `/usr/lib64/mpi/gcc/openmpi4/lib64/petsc/3.18.5/linux-gnu-c-opt/include/` - Shared lib and pkgconfig file: `/./usr/lib64/mpi/gcc/openmpi4/lib64/petsc/3.18.5/linux-gnu-c-opt/lib/` ... You get the idea. There is no predictability to determining paths to headers and libraries when using petsc as a dependency. Obviously, with the above setup, pkg-config goes out of the window and there is nothing to make up for it, no petsc-config binary or such. Imagine that petsc gets update to version 3.20.0, dependent packages have to modify their specfiles to get the include path right again. And please don't tell me to use gymnastics like: ``` %define petsc_version %(rpm -q --queryformat="%%{version}" petsc-openmpi4-devel) %define petsc_path %{openmpi_prefix}/%{_lib}/petsc/%{petsc_version}/linux-gnu-c-opt ``` Partly, I was looking into updating petsc to version 3.20.0, but the specfile scared me a little bit, I won't lie. -- You are receiving this mail because: You are on the CC list for the bug.