From: Caleb Herbert <csh@bluehome.net>
To: help-guix@gnu.org
Subject: mcron or mcron2?
Date: Wed, 22 Nov 2017 21:24:38 -0600 [thread overview]
Message-ID: <1511407478.4135.2.camel@leela> (raw)
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
I searched for mcron and got two versions that look identical but with
different deps. Which one should I get? I'm confused.
$ guix package -s mcron
name: mcron2
version: 1.0.8-0.31baff1
outputs: out
systems: x86_64-linux i686-linux armhf-linux aarch64-linux
mips64el-linux
dependencies: autoconf-2.69 automake-1.15 ed-1.14.2 guile-2.0.14
help2man-1.47.4 pkg-config-0.29.2 texinfo-6.3 which-2.21
location: gnu/packages/guile.scm:596:4
homepage: https://www.gnu.org/software/mcron/
license: GPL 3+
synopsis: Run jobs at scheduled times
description: GNU Mcron is a complete replacement for Vixie cron.
It is used to run tasks on a schedule, such as every hour or
every Monday. Mcron is written in Guile, so its
+ configuration can be written in Scheme; the original cron
format is also supported.
relevance: 4
name: mcron
version: 1.0.8
outputs: out
systems: x86_64-linux i686-linux armhf-linux aarch64-linux
mips64el-linux
dependencies: ed-1.14.2 guile-2.0.14 pkg-config-0.29.2
which-2.21
location: gnu/packages/guile.scm:570:2
homepage: https://www.gnu.org/software/mcron/
license: GPL 3+
synopsis: Run jobs at scheduled times
description: GNU Mcron is a complete replacement for Vixie cron.
It is used to run tasks on a schedule, such as every hour or
every Monday. Mcron is written in Guile, so its
+ configuration can be written in Scheme; the original cron
format is also supported.
relevance: 4
--
Caleb Herbert
OpenPGP public key: http://bluehome.net/csh/pubkey
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2017-11-23 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 3:24 Caleb Herbert [this message]
2017-11-23 15:01 ` mcron or mcron2? Leo Famulari
2017-11-23 17:02 ` Caleb Herbert
2017-11-24 0:52 ` Leo Famulari
2017-11-24 13:58 ` Ludovic Courtès
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=1511407478.4135.2.camel@leela \
--to=csh@bluehome.net \
--cc=help-guix@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.
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).