:: Re: [Dng] Devuan commitments - will…
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Anto
日付:  
To: dng
題目: Re: [Dng] Devuan commitments - will trade-off be applied?


On 18/03/15 15:52, Steve Litt wrote:
> >From my Manjaro Experiments experience, I would be neither surprised nor
> dissapointed if the first beta release of Devuan had some remaining
> systemd'isms. It's a step, in the right direction, on the journey
> toward complete independence from all things systemd.
>
> I'd also like to point out that the perfect is the enemy of the good. I
> fear that if we hold back release until every systemd'ism is gone,
> we'll never release. And the fact is, forever, Red Hat and their
> poetterproxy will be inserting new infections that can be removed, but
> not instantaneously.
>
> In summary, my personal opinion is 100% depoetterization is something
> we're working toward, but it's better not to let that hold back our
> releases, always assuming we're going in the right direction, which we
> most certainly are right now.
>
> SteveT
>
> Steve Litt                *  http://www.troubleshooters.com/
> Troubleshooting Training  *  Human Performance


Hello Steve,

I agree with you. I also expect that the initial release of Devuan might
still contain systemd components that I don't actually want to use, as a
trade-off of releasing Devuan as soon as possible. I can accept this
kind of trade-off.As long as the main intention of removing systemd
components is still intact, I am quite sure that we will get there
eventually. At the moment, I have packages from mixed repositories. I
will do the same if I saw packages from Devuan that still depends on
systemd components. I am sure that will gradually change so I believe
that I will finally only use Devuan repository.

What I am afraid of is that, along the line some powerful people in
Devuan will make a trade-off in using systemd components. For instance,
they decide to integrate a super-dupper package which requires systemd
components, e.g. for DE, which has nothing to do with any
functionalities of servers but the dependencies on systemd components
that have to be included in the repository only creates problems on the
servers.

I don't think I am narrow minded. I like the idea of systemd as init.
But about 2 months after I forcedly switched to systemd init as I used
Debian testing repository last year, I felt trapped and lost my freedom
to choose the packages to use and remove due to the maze dependencies to
systemd components. I chose Linux over Windows about 12 years ago even
Linux did not fully support the devices that I had, for the very reason
to have the freedom to choose what I want and I don't want to use. If I
lost that due to all Linux distros decide to use systemd and its
components, I would better of using Windows. I still don't see *BSD, OS
X, Solaris based OS, etc., to be my options yet until now.

Kind regards,

Anto