From: Leo Famulari <leo@famulari.name>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add rottlog.
Date: Fri, 17 Jun 2016 14:39:36 -0400 [thread overview]
Message-ID: <20160617183936.GA11491@jasmine> (raw)
In-Reply-To: <87lh23andj.fsf@gnu.org>
On Fri, Jun 17, 2016 at 04:41:44PM +0200, Jan Nieuwenhuizen wrote:
> It `builds' and installs...now to figure out how to configure and hook
> it up with mcron and how to run mcron.
Ludovic sent a WIP mcron service to guix-devel recently; you might take
a look at that. Alternatively, I run mcron for my user only and it works
as expected.
> * gnu/packages/logging.scm (rottlog): New variable.
> + (inputs `(("util-linux" ,util-linux) ; cal
> + ("texinfo" ,texinfo)))
> + (source (origin
> + (method url-fetch)
> + (uri (string-append "mirror://gnu/rottlog/rottlog-" version
> + ".tar.gz"))
> + (sha256
> + (base32
> + "0751mb9l2f0jrk3vj6q8ilanifd121dliwk0c34g8k0dlzsv3kd7"))
> + (patches (search-patches "rottlog.patch"))))
That patch is missing from this patch ;)
> + (arguments
> + '(#:configure-flags
> + (list (string-append "ROTT_ETCDIR=" %output "/etc/rottlog"))))
> + (build-system gnu-build-system)
Nit-picky, but I think the order should be: source, build-system,
arguments, inputs. At least, source should be first.
> + (description
> + "GNU Rot[t]log is designed to simplify administration of systems that
I think the description should contain the string "Rottlog" or
"rottlog", to make searching easier.
next prev parent reply other threads:[~2016-06-17 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 14:41 [PATCH] gnu: Add rottlog Jan Nieuwenhuizen
2016-06-17 18:39 ` Leo Famulari [this message]
2016-06-17 18:51 ` Jan Nieuwenhuizen
2016-06-18 1:50 ` Leo Famulari
2016-06-18 10:05 ` Jan Nieuwenhuizen
2016-06-19 13:51 ` Ludovic Courtès
2016-06-19 14:04 ` Jan Nieuwenhuizen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160617183936.GA11491@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=janneke@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.