From: Phil Blundell <pb@pbcl.net>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: oe-core layer <openembedded-core@lists.openembedded.org>, Patches
Subject: Re: [PATCH 1/7] bitbake.conf: fix definition of ${libexecdir}
Date: Tue, 30 Apr 2013 10:34:15 +0100 [thread overview]
Message-ID: <1367314455.14512.147.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <ly61z5c4j8.fsf@ensc-virt.intern.sigma-chemnitz.de>
On Tue, 2013-04-30 at 01:15 +0200, Enrico Scholz wrote:
> 1. ${prefix}/libexec
>
> --> clean separation, commonly used, but not FHS compliant (unless
> somebody interprets "/usr/lib<qual> : Alternate format libraries
> (optional)" with '<qual>=exec')
Actually, FHS 3.0 draft 1 does appear to admit the possibility of
libexec again:
http://www.linuxbase.org/betaspecs/fhs/fhs.html#usrlibexec
So maybe this option isn't (or won't be) so noncompliant as it might
first have appeared.
p.
prev parent reply other threads:[~2013-04-30 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 15:26 [PATCH 1/7] bitbake.conf: fix definition of ${libexecdir} Enrico Scholz
2013-04-29 15:26 ` [PATCH 2/7] bitbake.conf: fix libexecdir packaging Enrico Scholz
2013-04-29 15:26 ` [PATCH 3/7] connman: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 4/7] eglibc: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 5/7] uclibc: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 6/7] gstreamer: " Enrico Scholz
2013-04-29 15:26 ` [PATCH 7/7] gamin: " Enrico Scholz
2013-04-29 15:33 ` [PATCH 1/7] bitbake.conf: fix definition of ${libexecdir} Burton, Ross
2013-04-29 15:52 ` Enrico Scholz
2013-04-29 16:20 ` Burton, Ross
2013-04-29 17:03 ` Enrico Scholz
2013-04-29 22:33 ` Saul Wold
2013-04-29 23:15 ` Enrico Scholz
2013-04-30 9:34 ` Phil Blundell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1367314455.14512.147.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox