Re: systemd as external dependency
- From: Josselin Mouette <joss debian org>
- To: desktop-devel-list gnome org
- Subject: Re: systemd as external dependency
- Date: Wed, 18 May 2011 18:03:02 +0200
Le mercredi 18 mai 2011 à 17:30 +0200, Lennart Poettering a écrit :
> It's not just some #ifdefs. It's a ton. Lemme list a couple of Linux
> specific interfaces that are used in systemd, you'd have to find
> replacements for:
> - get_current_dir_name()
> - canonicalize_file_name()
(Just to be pedantic: these are from glibc, so are available with
kFreeBSD as well.)
> And this is just what I found while going through two files in
> systemd. Of course, a couple of these are easy to emulate, or have
> obvious counterparts on the other OSes, or could be made optinal (or
> even are already optional), but the point I want to make here is that it
> wouldn't be a couple of #ifdefs.
Sure, but what if people want to do the job?
> It would turn every second line of
> systemd into #ifdefs. And I wouldn't want to maintain such a beast.
> That all said, git is your friend. If people want to port this over to
> other systems, they are welcome to do so and with "git rebase" they
> could keep it somewhat up-to-date. I will not share your suffering if
> you do.
Ah right, people won’t do the job, because you give them the finger from
the very beginning. Sure. What could we need more right now than another
glibc/eglibc disaster with a maintainer who doesn’t want to care about
more than his chapel?
Note that this is the primary reason preventing us from making good use
of systemd features in Debian. This would imply, for each package
providing a daemon, to maintain a sysv init script for insserv a service
for systemd. So we’re stuck, at best, with using only the lowest common
denominator between init systems.
In the end, this behavior is not just making the life of porters
impossible; it is making harder to actually embrace your software.
.''`. Josselin Mouette
: :' :
] [Thread Prev