From: Joshua Lock <joshua.lock@collabora.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 8/9] nfs-utils: don't force use of /sbin as sbindir
Date: Thu, 03 Sep 2015 20:15:46 +0100 [thread overview]
Message-ID: <1441307746.2977.32.camel@collabora.co.uk> (raw)
In-Reply-To: <55E87FE5.8050406@windriver.com>
On Thu, 2015-09-03 at 12:14 -0500, Mark Hatle wrote:
> On 9/3/15 9:58 AM, Joshua Lock wrote:
> > In a system with a merged /usr /sbin isn't packaged.
>
> This sounds like an error to me if /sbin doesn't exist at all. It
> should exist
> either as a link to /usr/sbin (or the reverse).. but it should be
> there as lots
> of things expect the directory (or link) to exist.
Sure, it exists in my images but not during packaging. In my testing I
have base_bindir, base_libdir and base_sbindir set to children of /usr
in my distro.conf and a base-files_%.bbappend that creates the
symlinks. Therefore at packaging time the /sbin directory (and symlink)
doesn't exist.
I admit this commit message is pretty poor and I'll try and remember to
fix it in a v2.
Regards,
Joshua
> (It's also required by the FHS, even though that probably isn't
> enough of a
> concern.)
>
> > Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk>
> > ---
> > meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb | 8
> > ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb
> > b/meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb
> > index 6da8509..42101de 100644
> > --- a/meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb
> > +++ b/meta/recipes-connectivity/nfs-utils/nfs-utils_1.3.1.bb
> > @@ -90,6 +90,14 @@ RDEPENDS_${PN}-stats = "python"
> >
> > FILES_${PN} += "${systemd_unitdir}"
> >
> > +do_configure_prepend() {
> > + sed -i -e 's,sbindir = /sbin,sbindir = ${base_sbindir},g'
> > \
> > + ${S}/utils/mount/Makefile.am
> > +
> > + sed -i -e 's,sbindir = /sbin,sbindir = ${base_sbindir},g'
> > \
> > + ${S}/utils/osd_login/Makefile.am
> > +}
> > +
> > # Make clean needed because the package comes with
> > # precompiled 64-bit objects that break the build
> > do_compile_prepend() {
> >
>
> So my concern is simply with the commit msg -- not the actual
> implementation.
> What you have above looks correct to me.
next prev parent reply other threads:[~2015-09-03 19:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 14:58 [PATCH 0/9] Fixes for a distro with a merged /usr Joshua Lock
2015-09-03 14:58 ` [PATCH 1/9] kmod: fix link creation when base_bindir != /bin Joshua Lock
2015-09-03 14:58 ` [PATCH 2/9] busybox: fixes for " Joshua Lock
2015-09-03 14:58 ` [PATCH 3/9] systemd: remove hard-coded paths in FILES entries Joshua Lock
2015-09-03 15:12 ` Richard Purdie
2015-09-03 15:22 ` Burton, Ross
2015-09-03 19:16 ` Joshua Lock
2015-09-03 17:10 ` Mark Hatle
2015-09-04 11:07 ` Joshua Lock
2015-09-04 14:06 ` Burton, Ross
2015-09-03 14:58 ` [PATCH 4/9] alsa-utils: handle udev dir being 2 levels below / Joshua Lock
2015-09-03 14:58 ` [PATCH 5/9] pulseaudio: " Joshua Lock
2015-09-03 14:58 ` [PATCH 6/9] bluez: " Joshua Lock
2015-09-03 14:58 ` [PATCH 7/9] pcmciautils: " Joshua Lock
2015-09-03 14:58 ` [PATCH 8/9] nfs-utils: don't force use of /sbin as sbindir Joshua Lock
2015-09-03 17:14 ` Mark Hatle
2015-09-03 19:15 ` Joshua Lock [this message]
2015-09-03 14:58 ` [PATCH 9/9] procps: fix for base_sbindir == sbindir Joshua Lock
2015-09-03 17:11 ` [PATCH 0/9] Fixes for a distro with a merged /usr Mark Hatle
2015-09-03 19:10 ` Joshua Lock
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=1441307746.2977.32.camel@collabora.co.uk \
--to=joshua.lock@collabora.co.uk \
--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