Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
	Ross Burton <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Move systemd binaries to /sbin/systemd
Date: Mon, 15 Apr 2013 16:15:01 +0100	[thread overview]
Message-ID: <1366038901.8670.53.camel@ted> (raw)
In-Reply-To: <155F9D05-94DF-4B6B-8CC7-E75D22696C81@dominion.thruhere.net>

On Mon, 2013-04-15 at 13:21 +0200, Koen Kooi wrote:
> Op 15 apr. 2013, om 13:00 heeft Enrico Scholz <enrico.scholz@sigma-chemnitz.de> het volgende geschreven:
> 
> > Ross Burton <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > writes:
> > 
> >> Following the example set by udev, move the binaries to /sbin/systemd
> >> and hardcode less paths in general.  Tested on atom-pc with a .hddimg
> >> so the live boot/initrd paths were tested.
> > 
> > At least the moving of udev breaks a lot of local recipes here which
> > install e.g. local rules or keymaps in /lib/udev.  This is a silent break
> > which is detected at device runtime only.  The global 'bitbake.conf' has
> > not been updated for the new paths neither.
> > 
> > 
> > There should be:
> > 
> > 1. added some QA checks which detect this broken packaging
> > 
> > 2. added some global variables (e.g. 'udev_basedir') which can be used
> >   in the rules.
> 
> These patches can get NAK'd all you want, but they will go in. I still
> say: NAK, this is a bad, bad idea. It diverges from upstream and
> introduces silent breakage as you point out due to that.

In the 1.5 timeframe I want to look at this again and see how we can
better solve it as it may be we can do something to the multilib code to
avoid the issues. We ran out of runway with this for 1.4 :(.

Cheers,

Richard




  reply	other threads:[~2013-04-15 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 16:28 [PATCH 0/2] Move systemd binaries to /sbin/systemd Ross Burton
2013-04-11 16:28 ` [PATCH 1/2] systemd: move the " Ross Burton
2013-04-11 16:28 ` [PATCH 2/2] initrdscripts: look for new systemd-udevd location Ross Burton
2013-04-15 11:00 ` [PATCH 0/2] Move systemd binaries to /sbin/systemd Enrico Scholz
2013-04-15 11:21   ` Koen Kooi
2013-04-15 15:15     ` Richard Purdie [this message]
2013-04-15 15:58       ` Enrico Scholz

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=1366038901.8670.53.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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