From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Adding rottlog service in ‘%base-services’?
Date: Wed, 19 Oct 2016 17:03:58 +0200 [thread overview]
Message-ID: <87pomw7541.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_imm6WCyhbDRbyeW=_4S6C-GGA3zUiJ5ve3-Lh1DrRXpdsw@mail.gmail.com> (David Craven's message of "Thu, 13 Oct 2016 10:44:55 +0200")
David Craven <david@craven.ch> skribis:
>> Should we add rottlog-service and thus mcron-service to
>> ‘%base-services’? Is log rotation a basic feature that people expect?
>> WDYT?
>
> Why not. There's two sorts of people. The ones that don't care/know
> will be happy when things just work and the ones that care/know are
> probably defining their own %base-services anyway...
Yeah so I think ‘%base-services’ is bound to remain pretty much the same
forever.
And what about adding it to ‘%desktop-services’? This one is clearly
for people who expect things to work out of the box.
>> If we do so, we would need to document a way to add mcron jobs from the
>> ‘operating-system’ declaration. People would no longer be able to write
>> something like this in the ‘services’ field.
>
> Mmh... If we do something like this we shouldn't call it mcron-jobs,
> otherwise we'll have the same problems like with grub - where all
> variables are named grub or grub? or grub.cfg. How about just calling
> it jobs?
Not sure I understand the problem. ‘mcron-jobs’ wouldn’t collide with
anything else AFAICS, and it would be clearer than just ‘jobs’ no?
So related question: putting ‘mcron-service’ in ‘%base-services’? It
would be a no-op in the absence of job specifications.
Thanks for your feedback,
Ludo’.
next prev parent reply other threads:[~2016-10-19 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:24 Adding rottlog service in ‘%base-services’? Ludovic Courtès
2016-10-13 8:37 ` ng0
2016-10-13 8:44 ` David Craven
2016-10-19 15:03 ` Ludovic Courtès [this message]
2016-10-22 5:52 ` David Craven
2016-10-24 21:02 ` Ludovic Courtès
2016-10-25 12:53 ` David Craven
2016-10-13 8:40 ` Vincent Legoll
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=87pomw7541.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david@craven.ch \
--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).