Following MPI packaging guidelines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. I'm editing .spec file of MUMPS package to conform it to the MPI packaging guidelines (http://fedoraproject.org/wiki/Packaging:MPI). I have a modest experience in this particular case so I need some suggestions. This is initial .spec file of MUMPS: http://pkgs.fedoraproject.org/cgit/MUMPS.git/tree/MUMPS.spec This is that adjusted according to the MPI packaging guidelines: http://sagitter.fedorapeople.org/MUMPS/MUMPS.mod.spec As you see, I have created the packages - - MUMPS-openmpi - - MUMPS-openmpi-devel - - MUMPS-common Upstream provides illustrative test programs showing how MUMPS can be used in examples/ directory; Can I package these programs in 'MUMPS-common' package ? They are located in dedicated directory in /usr/share. 'MUMPS-openmpi' contains all versioned libraries; I don't know if it's correct or the package must be named 'MUMPS-openmpi-libs' Should all .h files be in a '-headers' subpackage ? Now, they are 'MUMPS-openmpi-devel'. This phrase in MPI guidelines is little clear for me: "Software that supports MPI MUST be packaged also in serial mode [i.e. no MPI], if it is supported by upstream." What does mean "serial mode" ? :) - Antonio Trande mailto: sagit...@fedoraproject.org Homepage: http://www.fedoraos.worpress.com GPG Key: D400D6C4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR7/rqAAoJED2vIvfUANbEKJIP/iaaHVdWkxrnVd+4CtbKPFU3 4LqdPNFuUMpzlsdNIyAPhkKnGHZiLTFoLg9kWOMw+SnM7gVhfHg5j081a/4io61k DiJhpoCOBHqoMM1RMYjII3bL07+N+VTliFo6MW7dVKTG2LUE47A/nC49P1cM77UN vh7pfLjc4F8sIrQO5ic3cxjT3s9+xpdbu+6ojNruwChomK47bY2AV9pzgRZUu76r Felx9hXZp10RsVegKB4SxjUqmxQi65scF71e2xBHKN82uPxO0a+ifNbfJjh9PZk/ YWXDjuABwtzJgRYW8alSJn/DAjnMHVyQJHzVynSmGsfWy6ffP3BSf8+kJk2TwvLs 7Mtue7DG/NAa08DYJWFAI/8lA8dvGx0NG1kPAFce0EOv+O0mCckOrQ78Vb50OG93 E0jkpib9at3DLz3iAVF5Sez9nzF0jKmo7MXuv0eCsYG22yYPoNjTSDo/6hEtxk9s HkV6Cr05S5tvT2VZp6KsVJs9bTCSrr39EFKhYz4fZO/qNY3WLN5PVhFMuu9mU+6H 37LqipT8GDQfneNAGF7yShQJxIe53hBnWSem/RnhcwXpWmYIILiKlBhNNEErOKUa buwUqaT8CxWjzZZZEb8dKE5ndt40N87fRkhdi8vaNxeNMRi8VWpjESsVSBPMlzdX vW+uGyYBIUH7QSYoYIDc =5kU6 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Following MPI packaging guidelines
On 24/07/13 05:04 PM, Antonio Trande wrote: This phrase in MPI guidelines is little clear for me: "Software that supports MPI MUST be packaged also in serial mode [i.e. no MPI], if it is supported by upstream." What does mean "serial mode" ? :) "Serial" in this case means "non-parallel", running without MPI. Regards, Dariusz -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Following MPI packaging guidelines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/24/2013 06:56 PM, Dariusz J. Garbowski wrote: > On 24/07/13 05:04 PM, Antonio Trande wrote: >> This phrase in MPI guidelines is little clear for me: >> >> "Software that supports MPI MUST be packaged also in serial mode >> [i.e. no MPI], if it is supported by upstream." >> >> What does mean "serial mode" ? :) > > "Serial" in this case means "non-parallel", running without MPI. > > Regards, Dariusz > Thank you Dariusz. Do you think new .spec file is already suitable ? - -- - Antonio Trande mailto: sagit...@fedoraproject.org Homepage: http://www.fedoraos.worpress.com GPG Key: D400D6C4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR8SflAAoJED2vIvfUANbE+rYQALeLM/7mYxqmPI9/mh8zC/ND AGgZz/owkUSG8EkaPTqRVzPTEQAo0mSbDx0dllt2FDwNPJ7BV1buWU40GD48GNBY fQyZEcD1DDazTgXXgIMZ+dmOqpTrmPQT7PwKdlyqSfp3KxI9dvJDHP3x2BKGzkSP eEm3UbKiKY7w0qnacz22LIp6bV0J7xq4JRy0NEwImoX5s8jl8Duuz/CCSuBXDnFe /3kQW+7plrVvM+10zW5HFhjzaO//fDxvZci2yqX4LPX+P7mjexAeGpeOty4D/zvj +4zPCBlnw5KHvRTHV9OrdGfRKKhdpOfG4i5LhCM03jHejCwW6xQFqE37Jd6YGtiC ZQn6MMzLdNC+rahFK4vCjoIc46adcnx4vt8JJ0F/erni63NZ8NEFIsj8L8GTkx1Z P9ld32HSwPLthunW3Lrv/c+LIkkrV/FzlWPZQIcHK4Owo9/beISwa0K7YfFajIm/ 1Dy3dOUp+lQ2EOumMIi1uta1gbf7DIxRfmGevFxedLfCG3lB4YjPCaI5v7etzQ0k wf1PNq3woQPEXwfm+t+jO0DXMFJmNH7g5lRiGnLCO5fZUpS3hjWT1MNpP3OJZc6x DB1YvY/YYP7dAU8NWRUe0q269Djm/I4HJ7G3S7gWJXTzOQU3nLS9N1H5MbAeK2sp ZAp/hp4T6hw4OAxDJTSx =tHA5 -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Following MPI packaging guidelines
> Hi all. > > I'm editing .spec file of MUMPS package to conform it to the MPI > packaging guidelines (http://fedoraproject.org/wiki/Packaging:MPI). I > have a modest experience in this particular case so I need some > suggestions. > > This is initial .spec file of MUMPS: > http://pkgs.fedoraproject.org/cgit/MUMPS.git/tree/MUMPS.spec > > This is that adjusted according to the MPI packaging guidelines: > http://sagitter.fedorapeople.org/MUMPS/MUMPS.mod.spec > > As you see, I have created the packages > > - - MUMPS-openmpi > - - MUMPS-openmpi-devel > - - MUMPS-common > > Upstream provides illustrative test programs showing how MUMPS can be > used in examples/ directory; Can I package these programs in > 'MUMPS-common' package ? They are located in dedicated directory in > /usr/share. > > 'MUMPS-openmpi' contains all versioned libraries; I don't know if it's > correct or the package must be named 'MUMPS-openmpi-libs' > > Should all .h files be in a '-headers' subpackage ? > Now, they are 'MUMPS-openmpi-devel'. > > This phrase in MPI guidelines is little clear for me: > > "Software that supports MPI MUST be packaged also in serial mode [i.e. > no MPI], if it is supported by upstream." > > What does mean "serial mode" ? :) MUMPS.mod.spec appears good. I would use the environment variables ($MPI_LIB and $MPI_INCLUDE) after module load mpi but the definitions should be good enough. About what is "serial mode", you should refactor MUMPS.spec to also make a build with openmpi disabled. Should do two builds in MUMPS.spec, and install the build that does not need "module load mpi" to work installed in %{_libdir}, and the one that needs, installed in $MPI_LIB > - > Antonio Trande Paulo -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Following MPI packaging guidelines
Hi! On Jul 24, 2013 9:04 AM, "Antonio Trande" wrote: > I'm editing .spec file of MUMPS package to conform it to the MPI > packaging guidelines (http://fedoraproject.org/wiki/Packaging:MPI). I > have a modest experience in this particular case so I need some > suggestions. > > This is initial .spec file of MUMPS: > http://pkgs.fedoraproject.org/cgit/MUMPS.git/tree/MUMPS.spec > > This is that adjusted according to the MPI packaging guidelines: > http://sagitter.fedorapeople.org/MUMPS/MUMPS.mod.spec > > As you see, I have created the packages > > - - MUMPS-openmpi > - - MUMPS-openmpi-devel > - - MUMPS-common > > Upstream provides illustrative test programs showing how MUMPS can be > used in examples/ directory; Can I package these programs in > 'MUMPS-common' package ? They are located in dedicated directory in > /usr/share. Yes, but usually examples are shipped in /usr/share/doc via %doc, not directly in /usr/share. > 'MUMPS-openmpi' contains all versioned libraries; I don't know if it's > correct or the package must be named 'MUMPS-openmpi-libs' No, a -libs subpackage would only be necessary if the main MUMPS-openmpi package contained more than libraries. > Should all .h files be in a '-headers' subpackage ? > Now, they are 'MUMPS-openmpi-devel'. No, -devel is the correct location for the headers. > This phrase in MPI guidelines is little clear for me: > > "Software that supports MPI MUST be packaged also in serial mode [i.e. > no MPI], if it is supported by upstream." > > What does mean "serial mode" ? :) -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Following MPI packaging guidelines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/25/2013 01:10 AM, Paulo César Pereira de Andrade wrote: >> >> What does mean "serial mode" ? :) > > MUMPS.mod.spec appears good. I would use the environment variables > ($MPI_LIB and $MPI_INCLUDE) after module load mpi but the > definitions should be good enough. > > About what is "serial mode", you should refactor MUMPS.spec to also > make a build with openmpi disabled. Should do two builds in > MUMPS.spec, and install the build that does not need "module load > mpi" to work installed in %{_libdir}, and the one that needs, > installed in $MPI_LIB > Hi Paulo. Good to hear from you again. :) Hi T.C. > Yes, but usually examples are shipped in /usr/share/doc via %doc, > not directly in /usr/share. 'examples' directory contains arch dependent programs, I can't packaging them in /usr/share. This .spec should be fine: http://sagitter.fedorapeople.org/MUMPS/MUMPS.mod2.spec - -- - Antonio Trande mailto: sagit...@fedoraproject.org Homepage: http://www.fedoraos.worpress.com GPG Key: D400D6C4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR8tvwAAoJED2vIvfUANbE+PIP/3qiJFKT5EHmIbRguqZqenZb pxT9kv6qZt9DMw/7gs11jECI/7QPkwxTx8ZA2WgJPDY3Dn3Ec49NGN7bUtXdhOJI 7XxzjuRi/l9D0RUJ+IP77O3ELMOFgRq1uPavsPD2lIdkBojJcEke2Itw9/dxhFGv JcyWbfQ2rPugLNLIb61makFlOaXKt4awCECgz8wuJ3dLjxRl+fJOWYMqLJkKAI1c D0jalI5az+dibzX4c2ZreD6YK9nolNrzuOfEWfhtKdGrTYAXC0uh2jTLpCzOxzBi Ne8oy6d9+se0Njsu0h65WqMUUKkD4p7nJeZhcukPQHO0ac7tav9oRurYjQ1fsUPk lWu2kKcnUxudITWPvIiKhSTBzD/AC6gb4znZIVTrbI4K2uZl54zS1MlvBye6xAVQ LTB88xiwfV38xTh/9cP+bsEN8NeJ1bpWtHbWUcJ608eGKQzU7JOQih/c2TROt4p4 I5Xt7VhunhxVPXIVjfZEI535/S0ErJ6HN+XnzqPzCEM36hVzU1ur3IL5BORlNuWU 2h+cJ07ZwfRK2ptmIyggQw8qzNc02zKuT7Ci+AMNPqsFYYPJX2OSip4wzgITAd57 94Fi8qkoHefRG3x5Ky9pSPCdfNDjqvY8/0KhbkAYTjR8rX+xrDQftlfl5AEGby0I A+xY7DjWQwHZWWoC0IAu =jTVj -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Following MPI packaging guidelines
On 7/26/13, Antonio Trande wrote: > 'examples' directory contains arch dependent programs, I can't > packaging them in /usr/share. In that case you could consider shipping them in an "-examples" subpackage if most consumers of the main package won't find them useful. Also, you could use %{_libexecdir} if you want the paths to these binaries to be the same on 32 and 64 bit systems. Both are optional though. > This .spec should be fine: > http://sagitter.fedorapeople.org/MUMPS/MUMPS.mod2.spec The -common subpackage should be "BuildArch: noarch" but otherwise it looks good. -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Following MPI packaging guidelines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Finished! http://koji.fedoraproject.org/koji/taskinfo?taskID=5664056 http://koji.fedoraproject.org/koji/taskinfo?taskID=5664100 Thank you all. - -- - Antonio Trande mailto: sagit...@fedoraproject.org Homepage: http://www.fedoraos.worpress.com GPG Key: D400D6C4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR8+MMAAoJED2vIvfUANbEs28QAMzrp2xPja1ELZGYWKvSnnN5 wE8Gzgc0OVajwQoBxAb1QYrbfKeQUufcLublm+VWMPGGpHyTNXIpITbntiTKi3PX 12YENMpbLrcisiVA0mhDa4kLmIUxPamG/PGh2qDEM4UzEKY5wDvIiowDonVUL+EL jDs0UzePwmFY2Fo/VDpixGv/pN2TQLV3HrnJTubdMXUV2Q92oJ2dV1x31Ojh/kjh 8aXmDs53H/3mITA6ET64NGLyYaqRhkucFAijSe3Ym9brOKuK5DGmaYa4wWW4B+z1 hrENM1k6oxb2n8ZYWFL1VjKq8Avpwt7qlyMEWPCdhhM6clQrIIN7UUKjG8Ia/x+7 ReKYEC++H1hn+CVxFDKSPsY7E30hFOPqUrkcnv/oySFvu1819HICgzb0rqheOtPv LVFmF/aGfg/tlcirwLGj6sbzpggknXHWQXWbaMsmnMAjTG6hNsPcVyUSuC4/ERug zWJBjYvN/qv8sZiJO/0ErJgVN9fbDuvKiSpNxUa1jWyw6WcJdB3zsN0MPDFvOMcE WdagWOfIJvOh8mwcVeINNw/vjg128Tu/zWz3BLX9tqkXtHuVvtbdKWlzASAA/FFG 1Q6Ahi1p13K8KDx/t5mE3GeA+7uT0Wd7lsjikifEzT/kKAVGJh10JahHdjgzepwU GQi063JzudaqLTafEKK0 =MrrI -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct