Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Bottazzini, Bruno" <bruno.bottazzini@intel.com>
To: Anders Darander <anders@chargestorm.se>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3 3/3] systemd: split modules into packages
Date: Mon, 11 May 2015 11:04:17 -0300	[thread overview]
Message-ID: <1431353057.3137.1.camel@bottazzini-ThinkPad-T430> (raw)
In-Reply-To: <20150511060614.GA13549@ad.chargestorm.se>

On Seg, 2015-05-11 at 08:06 +0200, Anders Darander wrote:
> * Bottazzini, Bruno <bruno.bottazzini@intel.com> [150508 00:46]:
> 
> > On Qui, 2015-05-07 at 20:58 +0200, Andreas Oberritter wrote:
> > > On 07.05.2015 18:40, Bruno Bottazzini wrote:
> > > > +                   vconsole \
> > > > +                   update \
> > > > +                   timesyncd \
> > > > +                   rfkill \
> > > > +                   quota \
> > > > +                   fuse \
> > > > +                   firstboot \
> > > > +                   dbus \
> > > > +                   binfmt \
> > > > +                   backlight \
> > > > +                   ask-password \
> 
> > > I think it may be better to sort this quite long list alphabetically.
> 
> > > Are these options already enabled today? 
> 
> > Yes, it is enabled. 
> 
> > This is the default packages enabled in the current recipe.
> 
> > > Because of the new
> > > packageconfig entries, I would have expected changes to EXTRA_OECONF and
> > > DEPENDS, which I don't see in your patch.
> 
> > Some packages does not have EXTRA_OECONF.
> 
> > You can see what this recipe DEPENDS by looking at ${PN}-services-base.
> 
> What Andreas is asking about, is e.g. for the kmod PACKAGECONFIG:
> 
> > > > +PACKAGECONFIG[kmod] = "--enable-kmod,--disable-kmod,kmod"
> 
> Here, if kmod is enabled in PACKAGECONFIG, kmod (the 3rd parameter),
> will be added to DEPENDS. Thus, you should remove kmod from the static
> DEPENDS (as now it's dynamically added using PACKAGECONFIGS).

You're right. I will make DEPENDS to be dynamically too.

> 
> The same is likely true for a number of the other PACKAGECONFIGs that
> you're adding (which, by the way is a _good_ thing to add).

Yeap! I will check the others

Thanks

> 
> Cheers,
> Anders
> 




      reply	other threads:[~2015-05-11 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 16:40 [PATCH V3 0/3] systemd: split modules into packages Bruno Bottazzini
2015-05-07 16:40 ` [PATCH V3 1/3] dbus: split tools package Bruno Bottazzini
2015-05-07 16:40 ` [PATCH V3 2/3] systemd: Verify if journal-flush.service exists Bruno Bottazzini
2015-05-07 18:49   ` Andreas Oberritter
2015-05-07 22:19     ` Bottazzini, Bruno
2015-05-07 16:40 ` [PATCH V3 3/3] systemd: split modules into packages Bruno Bottazzini
2015-05-07 18:58   ` Andreas Oberritter
2015-05-07 22:45     ` Bottazzini, Bruno
2015-05-11  6:06       ` Anders Darander
2015-05-11 14:04         ` Bottazzini, Bruno [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=1431353057.3137.1.camel@bottazzini-ThinkPad-T430 \
    --to=bruno.bottazzini@intel.com \
    --cc=anders@chargestorm.se \
    --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