Re: [gentoo-user] Debian just voted in systemd for default init system in jessie

[thegeezer <thegeezer@thegeezer.net>]

On 03/20/2014 06:42 PM, Tom Wijsman wrote:
> On Wed, 19 Feb 2014 10:19:43 +0000
> thegeezer <thegeezer@thegeezer.net> wrote:
>
>> the difficulty is that without knowing
> It is as easy as following the commits upstream makes, which is a
> short daily visit (or for less important followers, even weekly);
> that's really not too much asked for if you forked logind.
>
> It is even quite common practice and scriptable:
>
>     git fetch ... ; git log ... ; git diff ...
>
> In a similar way, I know Portage will get highlighting and a ^ indicator;
> without that being announced until release, here's a copy paste (note
> that what is above ^ would be colored in red, unwrapped to unbreak it):
>
> dev-lang/perl:0
>
>   (dev-lang/perl-5.18.2:0/5.18::gentoo, ebuild scheduled for merge) pulled in by
>     =dev-lang/perl-5.18* required by (virtual/perl-IO-1.280.0:0/0::gentoo, ebuild scheduled for merge)
>     ^              ^^^^^                                                                                                                                     
>
>   (dev-lang/perl-5.16.3:0/5.16::gentoo, installed) pulled in by
>     dev-lang/perl:0/5.16=[-build(-)] required by (dev-perl/IO-Socket-SSL-1.967.0:0/0::gentoo, installed)
>                  ^^^^^^^^                                                                                                                   
>     =dev-lang/perl-5.16* required by (virtual/perl-libnet-1.230.0:0/0::gentoo, installed)
>     ^              ^^^^^                                                                                                                        
>     (and 19 more with the same problems)
>
> And of course, that's not the only change happening; dependency
> resolution will become faster, some slot operator bug fixes happened
> but caused regressions in released versions and thus more of such fixes 
> will be done, some "no parents" messages during slot conflict output 
> were nuked, ...
>
> If I can type that as part of this mail, people could follow logind.
>

On 03/20/2014 06:42 PM, Tom Wijsman wrote:
> On Wed, 19 Feb 2014 10:19:43 +0000
> thegeezer <thegeezer@thegeezer.net> wrote:
>
>> the difficulty is that without knowing
> It is as easy as following the commits upstream makes, which is a
> short daily visit (or for less important followers, even weekly);
> that's really not too much asked for if you forked logind.
>
> It is even quite common practice and scriptable:
>
>     git fetch ... ; git log ... ; git diff ...
>
there's a slight misunderstanding here.
in a previous link on this list there was gnome developer that basically
said something like "we can't document everything that gnome uses in
systemd/logind because the developers are ahead of us, so in case of
difference the source code is correct".
gnome is big.  really big.
so you'd have to diff logind to check for new features and then diff
gnome to find how gnome is using those features.

so my point over 5 weeks ago was not about the difficulty in _finding_
the changes, but about keeping track of those changes and implementing htem.
if you read the rest of the thread you will see that in a whole i was
arguing that it is disingenuous to suggest that gnome does not require
logind.

if you don't see that perhaps you could volunteer to add logind api
features to openRC ?

btw, why did you reply to me cc the list instead of replying to list ?
i'm on the list already and so because of that my reply-to-list is broken.
it's easy enough to copy and paste the email address but please don't do
that again.