All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] system: add options for /bin /sbin and /lib to be symlinks into /usr
Date: Sat, 5 Sep 2015 14:13:08 +0200	[thread overview]
Message-ID: <20150905121308.GA3604@free.fr> (raw)
In-Reply-To: <55EAB410.1070300@mind.be>

Arnout, All,

On 2015-09-05 11:21 +0200, Arnout Vandecappelle spake thusly:
> On 04-09-15 22:17, Yann E. MORIN wrote:
> [snip]
> > diff --git a/package/eudev/eudev.mk b/package/eudev/eudev.mk
> > index 1aa74b3..a005f45 100644
> > --- a/package/eudev/eudev.mk
> > +++ b/package/eudev/eudev.mk
> > @@ -22,16 +22,18 @@ EUDEV_CONF_ENV += LIBS=-lrt
> >  EUDEV_CONF_OPTS =		\
> >  	--disable-manpages	\
> >  	--sbindir=/sbin		\
> > -	--with-rootlibdir=/lib	\
> >  	--libexecdir=/lib	\
> >  	--with-firmware-path=/lib/firmware	\
> >  	--disable-introspection			\
> > -	--enable-split-usr			\
> >  	--enable-libkmod
> >  
> >  EUDEV_DEPENDENCIES = host-gperf host-pkgconf util-linux kmod
> >  EUDEV_PROVIDES = udev
> >  
> > +ifeq ($(BR2_ROOTFS_MERGED_USR),)
> > +EUDEV_CONF_OPTS += --with-rootlibdir=/lib --enable-split-usr
> > +endif
>  It would be nice if someone could do a runtime test with eudev, both the merged
> and the split case.

I did.

The split-usr case is what we have had until now, and it works (I'm
using it daily with Kodi).

The merged-usr case I build-tested and slightly runtime-tested in the
same conditions (Kodi), and could see no difference in behaviour with
the split-usr case.

It's the systemd case that I did not runtime-test (only build-tested).

> >  ifeq ($(BR2_PACKAGE_EUDEV_RULES_GEN),y)
> >  EUDEV_CONF_OPTS += --enable-rule_generator
> >  endif
> > diff --git a/package/skeleton/skeleton.mk b/package/skeleton/skeleton.mk
> [snip]
> >  define SKELETON_INSTALL_TARGET_CMDS
> >  	rsync -a --ignore-times $(SYNC_VCS_EXCLUSIONS) \
> >  		--chmod=u=rwX,go=rX --exclude .empty --exclude '*~' \
> >  		$(SKELETON_PATH)/ $(TARGET_DIR)/
> > -	$(INSTALL) -m 0644 support/misc/target-dir-warning.txt \
> > -		$(TARGET_DIR_WARNING_FILE)
> > +	$(SKELETON_USR_SYMLINKS_OR_DIRS)
> >  	ln -snf lib $(TARGET_DIR)/$(LIB_SYMLINK)
> > -	mkdir -p $(TARGET_DIR)/usr
>  Huh, where did the mkdir go? Did you remove it because /usr is already in the
> skeleton?

Yes, it's not needed because we indeed already have it in the skeleton.
I should probably have said so in the commit log, indeed.

> >  	ln -snf lib $(TARGET_DIR)/usr/$(LIB_SYMLINK)
> > +	$(INSTALL) -m 0644 support/misc/target-dir-warning.txt \
> > +		$(TARGET_DIR_WARNING_FILE)
>  And why did you move this one around?

IMHO, it makes more sense to add it last, after the skeleton has been
entirely constructed. Granted, it's mostly eye-candy, still I find it
much nicer to look at this code now than as it was before.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2015-09-05 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 20:17 [Buildroot] [PATCHv3] system: add options for /bin /sbin and /lib to be symlinks into /usr Yann E. MORIN
2015-09-05  9:21 ` Arnout Vandecappelle
2015-09-05  9:44   ` Thomas Petazzoni
2015-09-05 12:13   ` Yann E. MORIN [this message]
2015-09-09 13:54 ` Mike Williams
2015-09-14 18:02   ` Mike Williams
2015-09-14 18:19     ` Yann E. MORIN
2015-10-14 21:14 ` Thomas Petazzoni

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=20150905121308.GA3604@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.