[Fedora-packaging] The role of %{_libexecdir} for using environment-modules

Ed Hill ed at eh3.com
Wed Oct 8 13:28:11 UTC 2008

On Wed, 08 Oct 2008 09:57:46 +0300 Jussi Lehtola wrote:
> On Tue, 2008-10-07 at 21:15 -0400, Ed Hill wrote:
> > 
> > *Please* stop suggesting alternatives.
> > 
> > Alternatives is a total failure for user-space applications that are
> > not *completely* generic and 100% interchangeable.  Lets illustrate
> > this point with three use cases:
> >
> > Please notice that modules (aka "environment modules") is a
> > perfectly workable solution for all the above scenarios and it does
> > not require any help from an admin (or root/sudo perms).
> Exactly. Now the question still remains where to hide these. OpenMPI
> puts its wrappers in /usr/share/openmpi, but /usr/share is for
> architecture independent data.
> Since /usr/bin doesn't have any subdirectories to me it seems quite
> straightforward to use /usr/libexec/%{name} to "hide" the binaries.
> They are then automatically added to the path upon loading the module.
> My interpretation is that this is OK according to the Packaging
> guidelines: "Libexecdir (aka, /usr/libexec on Fedora systems) should
> be used as the directory for executable programs that are designed
> primarily to be run by other programs rather than by users."


And +1 for a convention such as


that allows both names and, if desired, versions.


Edward H. Hill III, PhD  |  ed at eh3.com  |  http://eh3.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-packaging/attachments/20081008/83bf4991/attachment.sig>

More information about the Fedora-packaging mailing list