unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix-devel <guix-devel@gnu.org>
Subject: Adding ‘rottlog-service-type’ to ‘%base-services’
Date: Thu, 02 Apr 2020 19:18:22 +0200	[thread overview]
Message-ID: <87mu7tn6w1.fsf@inria.fr> (raw)

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

Hello Guix!

We discussed recently that we should add a ‘rottlog-service-type’
instance to ‘%base-services’.  It’s a trivial change that makes a lot of
sense to me.

It’s all fine but the problem is that it leads to a build failure of
etc.drv for those who were already adding ‘rottlog-service-type’ to
their services (because we end up with two instances of that service
type, both of which try to add /etc/rottlog.)

Perhaps that’s fine, and we can provide a news entry to let people now?

Incidentally, I think we should probably stop using GNU rottlog and
implement our own stuff: it wouldn’t be much work and would be much more
flexible (and we wouldn’t need that /etc/rottlog entry!).

Thoughts?

Ludo’.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 493 bytes --]

diff --git a/gnu/services/base.scm b/gnu/services/base.scm
index 8d9a563e2b..a0179c0259 100644
--- a/gnu/services/base.scm
+++ b/gnu/services/base.scm
@@ -2444,6 +2444,8 @@ to handle."
         (service guix-service-type)
         (service nscd-service-type)
 
+        (service rottlog-service-type)
+
         ;; The LVM2 rules are needed as soon as LVM2 or the device-mapper is
         ;; used, so enable them by default.  The FUSE and ALSA rules are
         ;; less critical, but handy.

             reply	other threads:[~2020-04-02 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 17:18 Ludovic Courtès [this message]
2020-04-02 18:28 ` Adding ‘rottlog-service-type’ to ‘%base-services’ Tobias Geerinckx-Rice
2020-04-03 11:37 ` Adding a %desktop-packages Joshua Branson
2020-04-06  8:01   ` Ludovic Courtès
2020-04-06  9:14     ` Gábor Boskovits

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=87mu7tn6w1.fsf@inria.fr \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    /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).