Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <luca.boccassi@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] systemd: enable portabled by default
Date: Mon, 13 May 2019 11:10:36 +0100	[thread overview]
Message-ID: <41ac4abea0dd66e99d21bdda69acd08ef81807e7.camel@gmail.com> (raw)
In-Reply-To: <CAMKF1spVZzywgp8PE3OuZ+x60tkyXgHCD3QpDfMfkVFefEMZrw@mail.gmail.com>

On Fri, 2019-05-10 at 09:45 -0700, Khem Raj wrote:
> On Fri, May 10, 2019 at 5:10 AM <
> luca.boccassi@gmail.com
> > wrote:
> > From: Luca Boccassi <
> > luca.boccassi@microsoft.com
> > >
> > 
> > portable services have been declared production ready with v241, so
> > enable
> > by default and install the files in the main package.
> > 
> 
> what is the rationale to enable it by default ?

Hi,

commit ada8a5d9175b disabled it by default because it was experimental:
"Add a new PACKAGECONFIG item 'portabled'. Default to disable it
because it's still experimental, according to the announcement letter."

Now it's been declared as stable by upstream, and also given machined
and nspawn are enabled by default I don't see a reason why this
shouldn't be as well, as they all provide the same "kind" of
feature/functionality, albeit on a different level.

> > Signed-off-by: Luca Boccassi <
> > luca.boccassi@microsoft.com
> > >
> > ---
> > v2: Just enable by default, and let the files be installed in the
> > main package
> >     as requested by reviewers.
> > 
> >  meta/recipes-core/systemd/systemd_242.bb | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/meta/recipes-core/systemd/systemd_242.bb
> > b/meta/recipes-core/systemd/systemd_242.bb
> > index 73e03c7a77..f15d125bf8 100644
> > --- a/meta/recipes-core/systemd/systemd_242.bb
> > +++ b/meta/recipes-core/systemd/systemd_242.bb
> > @@ -81,6 +81,7 @@ PACKAGECONFIG ??= " \
> >      nss \
> >      nss-mymachines \
> >      nss-resolve \
> > +    portabled \
> >      quotacheck \
> >      randomseed \
> >      resolved \
> > --
> > 2.20.1
> > 
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > 
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> > 
-- 
Kind regards,
Luca Boccassi



  reply	other threads:[~2019-05-13 10:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 21:40 [PATCH] systemd: enable portabled by default and install utilities in systemd-container luca.boccassi
2019-05-10  5:23 ` Martin Hundebøll
2019-05-10 10:45   ` Luca Boccassi
2019-05-10 10:46     ` Martin Hundebøll
2019-05-10 12:09 ` [PATCH v2] systemd: enable portabled by default luca.boccassi
2019-05-10 16:45   ` Khem Raj
2019-05-13 10:10     ` Luca Boccassi [this message]
2019-05-13 15:24       ` Khem Raj
2019-05-14 22:08         ` Luca Boccassi
2019-05-21 12:34 ` [PATCH v3] python*-setuptools: add separate packages for pkg_resources module luca.boccassi
2019-05-21 12:35   ` Luca Boccassi

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=41ac4abea0dd66e99d21bdda69acd08ef81807e7.camel@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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