[oe] [meta-systemd][PATCH V2 1/7] systemd: Upgrade to 187

Khem Raj raj.khem at gmail.com
Fri Aug 3 10:32:57 UTC 2012


On Aug 2, 2012, at 1:11 AM, Paul Eggleton <paul.eggleton at linux.intel.com> wrote:

> On Wednesday 01 August 2012 15:56:34 Khem Raj wrote:
>> On Aug 1, 2012, at 8:11 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>>>> Along with upgrade use the release tarballs instead of git
>>> 
>>> For an update we need to pull in some patches from master, so a git recipe
>>> is still the preferred way.
>> 
>> OK, you know more about it then me but do you know how many those will be ?
>> in other words does systemd releases mean much for stability yet or still
>> its a project moving at so fast pace ?
>> 
>> I see that releases are rolled out almost every month, that sort of could
>> mean either way, we wait until the next release or just take from a commit
>> upstream
>> 
>> I feel like staying with a release+patches could be one way if we are not
>> importing pathes too often. but I don't know how often that would be. For
>> the testing I did release worked well for those platforms x86, ppc and arm
> 
> One might suggest, if stable releases are working and you want to live on the 
> bleeding edge in your distro, you can easily do so there…

This is moving forward from where we were so it includes all the git commits that
were there until cd96b3b86abb4a88cac2722bdfb6e5d4413f6831 commit so this update
is inclusive.

we can also think of having a stable recipe and a git recipe but systemd releases
are almost a month apart it would be more or less covered if we moved from release
to release with some patches if needed.

thirdly we can have two recipes as Paul suggested.

> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre





More information about the Openembedded-devel mailing list