On Sun, Jan 9, 2011 at 4:19 AM, Leonid Batizhevsky <[email protected]> wrote:
> I think not need use upstart at 1.2.
> Pointlessly to rewrite scripts under the upstart and then in the next
I think it was already said that it's not pointless practice. From
what I gathered, integration work for the security framework
is partially done for upstart. And systemd isn't quite there yet.

Considering that the security framework is an important
feature planned for 1.2 release [1] and the release is planned
to be on a schedule, it makes sense to have upstart for 1.2.
The decision to use systemd in future [2] is also public info.

So that 1.2 (which will have security framework done) will have
upstart and have falling back on sysvinit has the contingency
plan. Going forward systemd integration work will be done with
the release target of 1.3 and onward.

That's what I understood from the discussion so far.

> version again put a lot of effort to adapt to systemd. Especially to
> 1.3 will already have done much in the Fedora community.
Not sure what you mean. Fedora also postponed using
systemd to F15 because the integration work wasn't ready
in time for F14. [3] As for MeeGo, main integration work,
the needed adjustments/enhancements and also the said
integration with the security framework are all yet to be
completed.

>
> PS: initV support parallel start and depends (see in debian)
>
> Leonid S. Batizhevsky
>
>
>
> On Fri, Jan 7, 2011 at 19:16, Arjan van de Ven <[email protected]> wrote:
snip
>>
>> actually systemd is a lot nicer in this regard, and they have some very
>> interesting features and tricks
>> to make that happen. Unfortunately, systemd on our schedule (hard feature
>> freeze in less than 2 weeks)
>> was just not an option, it's not quite ready for that.....
>>
See the point has already been made. :)

[1] http://bugs.meego.com/show_bug.cgi?id=8672
[2] http://wiki.meego.com/Architecture/Meetings/20101117_Weekly
[3] http://fedoraproject.org/wiki/Features/systemd

-- 
Gaveen Prabhasara
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to