On Thu, 2018-11-29 at 13:56:40 -0800, Josh Triplett wrote:
> Preferably in a package maintained by someone who actually uses that
> daemon with sysvinit, rather than one maintained by someone who doesn't.
> (And bugs in the use of that package with sysvinit then belong to that
> separate package, w
Josh Triplett writes:
> Ian Jackson wrote:
>> Stepping back a bit I think the ideal situation is this:
>>
>> * All packages have sysvinit scripts for compatibility.
>
> Preferably in a package maintained by someone who actually uses that
> daemon with sysvinit, rather than one maintained by some
Ian Jackson wrote:
> Stepping back a bit I think the ideal situation is this:
>
> * All packages have sysvinit scripts for compatibility.
Preferably in a package maintained by someone who actually uses that
daemon with sysvinit, rather than one maintained by someone who doesn't.
(And bugs in the
Russ Allbery writes ("Re: wicd-daemon-run_1.0_amd64.changes REJECTED"):
> I think a command would work for that case as well. What I'm imagining
> would look something like this:
Stepping back a bit I think the ideal situation is this:
* All packages have sysvinit scri
Lorenz writes:
> Ansgar Burchardt:
>>As a possible alternative: ship the runscript and some metadata (which
>>systemd service(s) and/or sysvinit script(s) this corresponds with;
>>which system users would be needed; ...) either in the service package
>>(preferred long-term) or a "runscripts" packag
Lorenz writes:
> That will work for runit-init, but what about runit-sysv and
> runit-systemd? Let's say I have systemd (as init), runit-systemd and a
> foo daemon installed; and 'runscripts' package ship a run script for
> foo. How can I detect if the user wants to manage foo with runit or with
Hi,
sorry for the extended quote, it's for reference in the debian-runit
mailing list (i'm subscribed there and you drop the CC)
Ansgar Burchardt:
>We generally try to avoid tiny packages in the archive; having 1000+
>automatically generated source and binary packages in the archive seems
>like a
]] Dmitry Bogatov
> which is provided by `-run' package:
>
> $ dpkg -L wicd-daemon-run
> [...]
> /etc/sv/wicd-daemon/log
> /etc/sv/wicd-daemon/log/run
> /etc/sv/wicd-daemon/run
> /var/log/runit/wicd-daemon
Does it also provide an init script? Else, it's RC b
On Wed, Nov 28, 2018 at 06:48:05PM +, Dmitry Bogatov wrote:
I believed (and still believe, despite of REJECT), that best way is
0. One source package, providing single binary package per runscript.
No, that's horrible. I agree with the REJECT.
Dmitry Bogatov writes:
> I believed (and still believe, despite of REJECT), that best way is
>
> 0. One source package, providing single binary package per runscript.
>
>src:{foo}-run -> bin:{foo}-run -> /etc/sv/{foo}
We generally try to avoid tiny packages in the archive; having 1000+
automat
[ Added runit maining list in thread ]
[2018-11-27 19:00] Bastian Blank
> All those *-run packages
> - are tiny (under 100 bytes of content),
> - generated (so why different source packages?) and
> - there sole purpose is providing support for another init system.
>
> Please let's reach consen
11 matches
Mail list logo
