This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libexecdir

Hash: SHA1

According to Corinna Vinschen on 6/10/2009 10:50 AM:
>> OTOH IMHO this is incorrect:
>> * libexec programs are not meant for direct execution by any user; sbin  
>> programs are (by superuser).
>> * libexec is often deep, which AFAIK /usr/sbin should not be per FHS.
>> There are a few other ways of handling libexec:
>> 1) GNU autotools uses /usr/libexec.  The problem is that is not  
>> FHS-compliant, which we generally try to be.
>> 2) Default to /usr/lib.  This will do the right thing when a package  
>> wants a subdir of libexecdir (e.g. git, gnupg, octave), but  
>> libexec_PROGRAMS will probably want to override that with a subdir 
>> thereof.
>> Thoughts?
> If FHS defines /usr/lib for libexecdir then I have no problems changing
> this for Cygwin as well.  It shouldn't even have any user-visible effect.

And for the few packages where it does matter, the packager can provide an
override in the .cygport file (just as I am now ending up doing to switch
libexecdir to /usr/lib as an override in my git.cygport).  I'm in favor of
making this change in cygport.

- --
Don't work too hard, make some time for fun as well!

Eric Blake   
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]