On Apr 10, 2013, at 4:39 AM, Andreas Müller <[email protected]> wrote:
> On Tue, Apr 9, 2013 at 10:01 PM, Martin Jansa <[email protected]> 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 <[email protected]> >>>> wrote: >>>>> On Wed, Feb 13, 2013 at 09:25:34AM -0800, Khem Raj wrote: >>>>>> Signed-off-by: Khem Raj <[email protected]> >>>>> >>>>> 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 >> I guess we're all too busy to implement 1), upgrade path would be nice, >> but is all-or-nothing, doesn't make much sense to spend a lot of time >> fixing every issue from PN-systemd when there are issues from other >> recipes we're not going to fix by .bbappends in meta-oe. >> >> Vote required from Khem, Koen, Andreas, Enrico, Otavio >> Vote welcome from other meta-systemd contributors >> > tend also to 3) + A) but I would prefer to have it as one transaction. > Otherwise we might face another upgrade path breakage. I know this > will cause questions as who and when… actually, 3+A is going to take some time I feel first 2 (without upgrade path) and then eventually 3+A would get us there > > Andreas _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
