unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>, Tissevert <tissevert+guix@marvid.fr>
Cc: guix-devel <guix-devel@gnu.org>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: GNU Guix 1.3.0rc1 available for testing!
Date: Wed, 05 May 2021 10:01:39 -0700	[thread overview]
Message-ID: <87v97xru6k.fsf@yucca> (raw)
In-Reply-To: <YJCWrkq7ClbU1vab@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]

On 2021-05-03, Leo Famulari wrote:
> On Mon, May 03, 2021 at 09:38:56PM +0200, Tissevert wrote:
>> I've just given the binary tarball a spin on Devuan. Worked almost flawlessly
>> (daemonize wasn't installed and I missed the part when it was mentioned because
>> I was a bit in a hurry but apart from that the overall experience was great —
>> the guix text art was surprising in a good kind of way).
>
> I think that a big part of why we offer the SysV-init "/etc/init.d"
> service management script is to serve Devuan — there are not many
> distros using that style of service management anymore.

Out of the *five* bug reports the guix packages in Debian received,
*two* of them were related to using SysV init (or at least not using
systemd):

  https://bugs.debian.org/974751
  https://bugs.debian.org/983248

So while Debian defaults to systemd, there is still the ability to
choose between init systems, and some people do explore that option.

I also just noticed some openrc scripts available too...


> If `daemonize` is not available by default on Devuan, I wonder if
> there is some other way we should be writing the script.

Yeah, not sure what best practices are for SysV init scripts these
days. For Debian I just documented that users of SysV in debian should
install daemonize; in future versions I may make it a soft alternate
dependency to the relevent systemd packages.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2021-05-05 17:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  5:45 GNU Guix 1.3.0rc1 available for testing! Maxim Cournoyer
2021-05-01  7:48 ` Vagrant Cascadian
2021-05-02  2:53   ` Maxim Cournoyer
2021-05-01 21:25 ` Leo Famulari
2021-05-02  2:52   ` Maxim Cournoyer
2021-05-02  4:27     ` Leo Famulari
2021-05-04  4:02       ` Maxim Cournoyer
2021-05-02  4:05   ` Leo Famulari
2021-05-02  4:28     ` Leo Famulari
2021-05-02 18:45     ` Maxim Cournoyer
2021-05-02 22:14       ` Leo Famulari
2021-05-03 19:38 ` Tissevert
2021-05-04  0:34   ` Leo Famulari
2021-05-05  8:16     ` Tissevert
2021-05-05 17:01     ` Vagrant Cascadian [this message]
2021-05-06  1:18       ` Leo Famulari
2021-05-05  1:49 ` Chris Marusich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v97xru6k.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=maxim.cournoyer@gmail.com \
    --cc=tissevert+guix@marvid.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).