On Mon, Dec 30, 2013 at 04:51:55PM +, Ian Jackson wrote:
> Steve Langasek writes ("Bug#727708: systemd and upstart, a view from a daemon
> Debian maintainer"):
> > I also think that the extensive maintainer script changes required for any
> > upstart-using
Steve Langasek writes ("Bug#727708: systemd and upstart, a view from a daemon
Debian maintainer"):
> I also think that the extensive maintainer script changes required for any
> upstart-using package are quite deplorable (whether or not they're wrapped
> in a helper sc
On Sat, Dec 28, 2013 at 03:56:49PM -0800, Russ Allbery wrote:
> > Also, the approach to the systemd integration introduces a new runtime
> > package dependency on "init-system-helpers", which despite its
> > generic-sounding name actually contains only helpers for systemd and is
> > maintained in D
Steve Langasek writes:
> Packages are shipping systemd units in the archive today, and Policy
> *should* cover this case. Currently, it covers this by saying "you can
> integrate with systemd, but must still provide compatibility with
> sysvinit", which I think is fine at this stage.
I think it
Steve Langasek writes:
> On Sun, Dec 29, 2013 at 12:42:24AM +0100, Vincent Bernat wrote:
>> Ian Jackson writes:
>>> The package maintainer scripts exposed more complexity too. It was
>>> necessary to add new systemd-specific calls to "deb-systemd-helper".
>>> The boilerplate required here was t
On Sun, Dec 29, 2013 at 12:29:50AM +0100, Josselin Mouette wrote:
> But this is even more troubling:
> > There was less support from the Debian policy manual. Perhaps there
> > is some other systemd Debian packaging guidance somewhere which I
> > didn't find.
> Incorporating upstart packaging i
On Sun, Dec 29, 2013 at 12:42:24AM +0100, Vincent Bernat wrote:
> ❦ 28 décembre 2013 23:46 CET, Ian Jackson :
> > The package maintainer scripts exposed more complexity too. It was
> > necessary to add new systemd-specific calls to "deb-systemd-helper".
> > The boilerplate required here was too
Ian Jackson writes:
> I found configuring upstart to be utterly trivial. There was little
> opportunity for error. More guidance in debian-policy would be a good
> idea, including perhaps a reference to some example packages.
I have a much longer message that goes into detail about what I foun
❦ 28 décembre 2013 23:46 CET, Ian Jackson :
> The package maintainer scripts exposed more complexity too. It was
> necessary to add new systemd-specific calls to "deb-systemd-helper".
> The boilerplate required here was too much to simply include in my
> existing scripts, so I had to switch the
Hi,
Le samedi 28 décembre 2013 à 22:46 +, Ian Jackson a écrit :
> In this message I'll deal with the config fragments ("units" and "jobs"
> as they call them), and the Debian-specific packaging.
It is probably needless to say that I disagree with about 99% of what
you wrote in tonight’s repo
As I have mentioned, I tried adapting userv to systemd and upstart. I
have already reported on my experience with the core daemon code.
In this message I'll deal with the config fragments ("units" and "jobs"
as they call them), and the Debian-specific packaging.
I'm treating the config fragments
11 matches
Mail list logo
