>>>>> Bastian Blank <wa...@debian.org> writes:
>>>>> On Sat, Oct 20, 2018 at 06:54:07PM +0200, Arne Babenhauserheide wrote:
>>>>> Ansgar Burchardt <ans...@debian.org> writes:
>>> Should Debian also support “noalsa”, “noavahi”, “nocups”,
>>> “nopulseaudio”, “nosysvinit”, “nodbus”, “nopam”, “nowayland”,
So long as there’s sufficient interest among the developers?
Sure, why not?
>> Are alsa, avahi, cups, pulseaudio, sysvinit, dbus, pam and wayland
>> all similar in scope to systemd? If not, then this question is a
>> strawman.
> Yes, they all completely took over their field and have a lot of haters.
AFAICT, that’s, for the most part, untrue. For instance, I do
/not/ run Avahi (why for?), Cups (I use an ad-hoc wrapper around
foo2zjs instead), Pulseaudio (for there’s ALSA, but also NAS and
JACK should I need them), D-Bus (although I admit I’ve had to
implement a “no-dbus.perl” stub non-server to work around
Bug#868453), or Wayland (huh?) And I suppose those who run
Systemd don’t run SysVinit just as well.
Granted, I know of no way to use audio on Debian GNU/Linux without
ALSA; and I know of no way to avoid running PAM, either.
Now, unless I be mistaken, “build profiles,” as suggested in
this subthread, are meant to allow for building packages with
specific changes to their run-time library dependencies?
Frankly, I don’t see much of a problem with that – assuming that
the libraries are “well-behaving,” that is. I can see an
application's run-time dependency on the presence of client
PostgreSQL, MySQL and MS SQL libraries at run-time as necessary
evil. Having that application pull one or more of the respective
servers per Depends: is something I tend to consider a bug.
(BTW, while we're at it, could someone please explain me what
tinysshd [1] does need systemd for? Or why installing neomutt
has to invite gnupg along?)
[1] http://packages.debian.org/sid/tinysshd
--
FSF associate member #7257 np. Green Beret (title theme) — Johan Andersson
