The question of rolling release?

[Reindl Harald]

Am 24.01.2012 17:37, schrieb Michal Schmidt:
> On 01/24/2012 05:17 PM, Reindl Harald wrote:
>> when i see that services which was not converted to systemd
>> needs features which were not available with the systemd
>> of F15 this is a clear sign that systemd was NOT ready for
>> a GA release
> 
> That missing feature is "PathExistsGlob=", isn't it?
> So the solution is easy - just have cups.service start the classical way: by pulling it into the default target.
> Cups worked without path-based activation when it was a SysV service and it can work just the same as a native
> service.

well, you can not do a simple "rpmbuild --rebuild cups.src.rpm.fc16"
it makes life harder

>> so updates should make it ready for GA
>>
>> how do you imagine that even maintainers could have
>> converted services for the F15 release with a
>> non-finished systemd-version?
> 
> I am amazed at the sophistry of the argument.
> 
> We sometimes add new features to systemd that service writers might find convenient to 
> use in their unit files. I guess that does make systemd "non-finished" when 
> interpreted literally.

yes because anybody who does not upgrade on the first release
day for very good reasons has to live with missing options

> What follows from that when it comes to suitability for a release? 
> Absolutely nothing.

if F15 would get the new features all would be fine but it does not, it
was a shot in the dark with only a few services converted and nothing
changes until the next dist-upgrade

after all the troubles i had only with mysqld based services and
F15 you should understand that i hestitate to make a F16 upgrade
where as example GRUB2 is introduced without a automatic transition
resulting in grubby always whining about a missing template (whatever
that means) on each kernel update, no idea how a "grub-install /dev/sda-/dev/sdd"
for systems booting form RAID1 devices should be done and such questions
which needs time to find out and test

in my opinion if core-subsystems are rewritten they should get updates
on a regular base at least for the initial release and not stay as
they where



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120124/8d31b616/attachment.sig>