From: ludo@gnu.org (Ludovic Courtès)
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: guix-devel@gnu.org
Subject: Re: Add Mercurial to version-control.scm
Date: Sat, 07 Sep 2013 15:06:20 +0200 [thread overview]
Message-ID: <87r4d06asz.fsf@gnu.org> (raw)
In-Reply-To: <8738piqor3.wl%arne_bab@web.de> (Arne Babenhauserheide's message of "Fri, 06 Sep 2013 11:32:32 +0200")
Hi Arne,
Arne Babenhauserheide <arne_bab@web.de> skribis:
> Here’s a patch to add Mercurial as package:
Thanks for the patch!
It looks good overall. I’m assuming that it actually builds, is usable,
and that you assert that you did a reasonable auditing setting the
‘license’ field.
A few stylistic comments.
First, could you send the patch as produced by ‘git format-patch’, which
a ChangeLog-style commit log (see ‘HACKING’ and the VCS history for
details)? Then we’ll happily push it. :-)
> +(define-public mercurial
> + (package
> + (name "mercurial")
> + (version "2.7.1")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (string-append "http://mercurial.selenic.com/release/mercurial-" version ".tar.gz"))
Please keep lines below 80 columns (see ‘Coding Style’ in ‘HACKING’.)
> + (sha256
> + (base32
> + "121m8f7vmipmdg00cnzdz2rjkgydh28mwfirqkrbs5fv089vywl4"))))
> + (build-system python-build-system)
> + (home-page "http://mercurial.selenic.com")
> + (synopsis "Decentralized version control system")
> + (description
> + "Mercurial is a free, distributed source control management tool.
> +It efficiently handles projects of any size and offers an easy and intuitive interface.")
Likewise.
> I put Mercurial between bazaar and subversion to keep alphabetic
> ordering. Later items might not be ordered alphabetically, but that’s
> out of my responsibility :)
Yes, we’re pretty liberal in that regard. ;-)
Thanks for your patch, and welcome aboard!
Ludo’.
prev parent reply other threads:[~2013-09-07 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 9:32 Add Mercurial to version-control.scm Arne Babenhauserheide
2013-09-07 13:06 ` Ludovic Courtès [this message]
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=87r4d06asz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=arne_bab@web.de \
--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).