|
|
Subscribe / Log in / New account

Debian, Rust, and librsvg

Debian, Rust, and librsvg

Posted Nov 15, 2018 14:55 UTC (Thu) by rschroev (subscriber, #4164)
In reply to: Debian, Rust, and librsvg by glaubitz
Parent article: Debian, Rust, and librsvg

Here's my view on why the init system debate generated much more conflict than librsvg.

Firstly, it's a different kind of debate.
Regarding the init system, the options where:
- keep sysvinit
- switch to systemd
- switch to upstart (IIRC)
Regarding librsvg, the options are:
- keep up to date with upstream
- don't keep up to date with upstream
(unless I'm missing something)
Is it a good thing that upstream switched to Rust? Maybe, maybe not, but it's not like Debian has much to say in it: it's upstream's decision.

Secondly, the importance. The choice of init system has its implications for the whole system, for all systems. The choice of librsvg only has impact on systems that use it. Perhaps that is a lot of systems, but demonstrably less. (Case study: at work we made software that runs aboard ships of a client of ours, collecting all kinds of data from sensors and sending that to a number of onshore servers. It runs on Debian, and I checked: no librsvg installed or needed. So no, I don't think librsvg is a core component as you claim).


to post comments

Debian, Rust, and librsvg

Posted Nov 16, 2018 2:57 UTC (Fri) by sorpigal (guest, #36106) [Link]

There's also this: the initd affects everyone. The SVG library doesn't. That will always make the former a bigger deal warranting more discussion.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds