On 09.08.2015 12:02, Rainer Weikusat wrote:
> Mark S Bilk <mark@???> writes:
>> It seems to me that it's good to have shim programs that satisfy
>> dependencies of apps on systemd, each shim performing some systemd
>> function. Here's why:
>>
>> Suppose there are 10,000 application programs (apps) for Linux,
>> and their developers foolishly insert dependencies on systemd.

These 10.000 apps with depencies could become 10.000 debian packages
with hard dependency to systemd. But if devuan removes the dependency
once they could create a patch and use this patch automatically on the
updated debian package...

debian pkg xy -> devuan developer -(creates)-> devuan package and devuan
patch;
debian upgrades pkg xy -> devuan build system applies the old patch -(if
no errors)-> package goes into testing...


I hope this is understandable. I think in most cases one patch could
uphold for a long time. Please think about that and stop developing
shims :) All those shims will end up in having a systemd fork.


>
> [...]
>
>> So using a relatively small number of shim programs in Devuan
>> will save an enormous amount of work for the Devuan developers,
>> which will allow them to use their time for more productive
>> purposes -- making Devuan more generally useful and attractive,
>> thereby gaining far more users.
>
> The end result of reimplementing systemd one-shim-at-a-time won't be
> distinguishable from just using systemd, minus the enormous amount of
> time wasted implementing all the shims. Since you frame this as
> unavoidable, you're thus effectively advocating use of systemd.



> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>