On Sat, Feb 6, 2010 at 7:38 AM, Jonas Karlsson <cj.karls...@gmail.com> wrote:
> On 5 February 2010 18:56, Lucas C. Villa Real <luca...@gobolinux.org> wrote:
>> On Fri, Feb 5, 2010 at 3:33 PM,  <mohj...@svn.gobolinux.org> wrote:
>>> Author: mohjive
>>> Date: 2010-02-05 09:33:15 -0800 (Fri, 05 Feb 2010)
>>> New Revision: 4331
>>>
>>> Modified:
>>>   branches/015/Scripts/Functions/Bootstrap
>>> Log:
>>> As 'libexec' is not part of FHS there's no point for us using it
>>
>> Hmm. I've seen some applications installing files in $target/libexec.
>> Maybe those had a broken Recipe/Makefile?
>>
> jo...@atlas /Files/015/LiveCD]find Output/ROLayer/Programs -name libexec
> jo...@atlas /Files/015/LiveCD]
>
> Nothing on the current CD at least. PrepareProgram is changed to pass
> --libexecdir=${target}/lib/$(Downcase ${appname}). Makefiles is
> another issue, but apparantly none is broken/I've fixed them.
I still don't like overloading a directory that (frequently) already
exists with some other purpose. I would prefer some other pattern be
used to avoid any potential clashes. Programs can have libraries and
libexec binaries with the same names, or worse, subdirectories. It
just doesn't seem sensible to risk that unnecessarily when it could
easily be changed to something non-conflicting.
-Michael
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to