Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] systemd: remove udev-extraconf from RRECOMMENDS
Date: Sun, 14 Apr 2013 16:59:51 +0200	[thread overview]
Message-ID: <20130414145951.GE2475@jama> (raw)
In-Reply-To: <7E440FB0-F32A-4E9F-A849-339B3102CF7C@dominion.thruhere.net>

[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]

On Sun, Apr 14, 2013 at 04:21:15PM +0200, Koen Kooi wrote:
> 
> Op 14 apr. 2013, om 16:05 heeft Martin Jansa <martin.jansa@gmail.com> het volgende geschreven:
> 
> > On Sun, Apr 14, 2013 at 03:55:22PM +0200, Koen Kooi wrote:
> >> In the original udev and systemd updates these extra conf rules and scripts where removed and moved to a different recipe to avoid pulling them in by default, making them opt-in. The systemd merge into oe-core regressed this into making it impossible to opt out of it when using package feeds for upgrades.
> >> 
> >> Change it back to opt-in for images/packagegroups.
> > 
> > Maybe RSUGGESTS?
> 
> Not sure if that fixes the case where people do want it. I explicitly don't want this ending up in my rootfs (BAD_RRECOMMENDS might work here), but that doesn't work when doing 'opkg upgrade'. 

It does not, but it will build udev-extraconf in feed and notify user
that there is "more" in case he decides to install udev-extraconf
manually.

> I'm just trying to fix regressions compared to the meta-oe udev/systemd state in 1.3 :)

I guess we all are :)

> >> ---
> >> 
> >> Since udev-extraconf is persona non grata in angstrom I have no idea what depends on it, so please tell me what needs to get fixed after removing this.
> >> 
> >> meta/recipes-core/systemd/systemd_199.bb | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >> 
> >> diff --git a/meta/recipes-core/systemd/systemd_199.bb b/meta/recipes-core/systemd/systemd_199.bb
> >> index 0d07f85..fbf2a2f 100644
> >> --- a/meta/recipes-core/systemd/systemd_199.bb
> >> +++ b/meta/recipes-core/systemd/systemd_199.bb
> >> @@ -202,7 +202,7 @@ FILES_udev-dbg += "/lib/udev/.debug"
> >> 
> >> RDEPENDS_udev += "udev-utils"
> >> RPROVIDES_udev = "hotplug"
> >> -RRECOMMENDS_udev += "udev-extraconf udev-hwdb"
> >> +RRECOMMENDS_udev += "udev-hwdb"
> >> 
> >> FILES_udev += "${base_sbindir}/udevd \
> >>                ${base_libdir}/systemd/systemd-udevd \
> >> -- 
> >> 1.8.1.4
> >> 
> >> 
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> > 
> > -- 
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 13:55 [RFC][PATCH] systemd: remove udev-extraconf from RRECOMMENDS Koen Kooi
2013-04-14 14:05 ` Martin Jansa
2013-04-14 14:21   ` Koen Kooi
2013-04-14 14:59     ` Martin Jansa [this message]
2013-04-15 10:03 ` Burton, Ross
2013-04-15 10:12   ` Koen Kooi

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=20130414145951.GE2475@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --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