Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: "koen@dominion.thruhere.net" <koen@dominion.thruhere.net>,
	"otavio@ossystems.com.br" <otavio@ossystems.com.br>,
	"enrico.scholz@sigma-chemnitz.de"
	<enrico.scholz@sigma-chemnitz.de>
Subject: Re: meta-systemd future vote Was: [meta-systemd][PATCH 1/2] Delete systemd class.
Date: Sat, 13 Apr 2013 13:29:42 +0200	[thread overview]
Message-ID: <20130413112942.GD2477@jama> (raw)
In-Reply-To: <20130412170255.GS2477@jama>

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

On Fri, Apr 12, 2013 at 07:02:55PM +0200, Martin Jansa wrote:
> On Wed, Apr 10, 2013 at 05:51:43PM -0700, Khem Raj wrote:
> > On Wednesday, April 10, 2013, Andreas Müller <schnitzeltony@googlemail.com>
> > wrote:
> > > On Tue, Apr 9, 2013 at 10:01 PM, Martin Jansa <martin.jansa@gmail.com>
> > wrote:
> > >> On Tue, Mar 05, 2013 at 11:59:07PM +0100, Martin Jansa wrote:
> > >>> On Tue, Mar 05, 2013 at 11:50:41PM +0100, Andreas Müller wrote:
> > >>> > On Tue, Mar 5, 2013 at 11:18 PM, Martin Jansa <martin.jansa@gmail.com>
> > wrote:
> > >>> > > On Wed, Feb 13, 2013 at 09:25:34AM -0800, Khem Raj wrote:
> > >>> > >> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > >>> > >
> > >>> > > good old meta-systemd should now parse again,
> > >>> > Thanks - will come back to test HEADs soon.
> > >>>
> > >>> But be aware that I've fixed only parsing of avahi and wpa-supplicant.
> > >>>
> > >>> I haven't tested it properly in runtime because my upgrade path is a bit
> > >>> broken (because I was building images with khem's patches for a while to
> > >>> test other stuff) and even clean build with failed to boot with
> > >>> qemux86-64 and I don't have time to debug it now.
> > >>>
> > >>> > > I wont apply this 2 commits
> > >>> > > until systemd discussion in oe-core is finished and future of
> > >>> > > meta-systemd decided.
> > >>> > >
> > >>> > After systemd regression is worked around yocto 1.4 release regression
> > >>> > is knocking at the door...
> > >>>
> > >>> yes :/
> > >>>
> > >>> If we need to maintain meta-systemd bbappends for upgrade path we can
> > >>> also maintain them with PN-systemd packages and good old systemd
> > bbclass.
> > >>
> > >> Khem pinged me about this patch, so here are my thoughts:
> > >>
> > >> PN-systemd discussion in oe-core haven't moved a bit since this patch
> > >> was proposed, I think we have 2-3 options, lets vote about meta-systemd
> > future.
> > >>
> > >> 1) keep PN-systemd separation in meta-systemd and fixup .bbappends to
> > >> resolve issues created by oe-core (I've fixed some issues, but still a
> > >> lot of issues in postinst/postrm/prerm scripts when both inits are
> > >> sharing the same PN)
> > >>
> > >> 2) give up on clean separation of PN-<init> and provide upgrade path
> > >> from PN-systemd to PN (mostly done by these 2 commits from khem).
> > >>
> > >> 3) give up on clean separation of PN-<init> and upgrade path (there are
> > >> many issues in other parts of oe-core, so upgrade path from danny to
> > >> dylan doesn't look usable.
> > >>
> > >> A) migrate existing .bbappends to their recipes to .bb files and
> > >> remove this layer. Any volunteer for that?
> > >>
> > >> My vote: 3) + A) later in 1.5
> > > A bit off-topic and mentioned here & there: I am working on
> > > network-manager(-applet) 0.9.8.0 update and xinput-calibrator. I could
> > > add 3) + A) for them if agreed. Hope to send them beginning of next
> > > week.
> > >
> > 
> > Sure I see no problem
> 
> OK, all systemd related changes should be now in master.
> 
> I'll do A) for meta-efl.
> 
> If someone starts working on A) for some other recipes, please write reply 
> here so that we don't duplicate work.

OK, I'll take care of A) for other layers too, just please review them.

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

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

      reply	other threads:[~2013-04-13 11:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 17:25 [meta-systemd][PATCH 1/2] Delete systemd class Khem Raj
2013-02-13 17:25 ` [meta-systemd][PATCH 2/2] meta-systemd: Append ${PN} to SYSTEMD_SERVICE Khem Raj
2013-02-14  3:01   ` Martin Jansa
2013-02-15 18:34     ` Khem Raj
2013-02-14  7:45   ` Martin Jansa
2013-02-15 18:39     ` Khem Raj
2013-04-13 14:56       ` Martin Jansa
2013-03-05 22:18 ` [meta-systemd][PATCH 1/2] Delete systemd class Martin Jansa
2013-03-05 22:50   ` Andreas Müller
2013-03-05 22:59     ` Martin Jansa
2013-04-09 20:01       ` meta-systemd future vote Was: " Martin Jansa
2013-04-09 20:06         ` Otavio Salvador
2013-04-09 20:08         ` Koen Kooi
2013-04-10 11:06           ` Burton, Ross
2013-04-10 21:17             ` Martin Jansa
2013-04-11  9:59               ` Burton, Ross
2013-04-10 11:39         ` Andreas Müller
2013-04-10 14:55           ` Khem Raj
2013-04-11  0:12         ` Andreas Müller
2013-04-11  0:51           ` Khem Raj
2013-04-12 17:02             ` Martin Jansa
2013-04-13 11:29               ` Martin Jansa [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=20130413112942.GD2477@jama \
    --to=martin.jansa@gmail.com \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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