unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@openmailbox.org>
To: ludo@gnu.org
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Add guile-minikanren
Date: Thu, 23 Apr 2015 14:48:50 -0500	[thread overview]
Message-ID: <5683758a81dab8c8c4a07b4b76944938@openmailbox.org> (raw)
In-Reply-To: <87d22uekq5.fsf@gnu.org>

On 2015-04-23 13:57, ludo@gnu.org wrote:
>>>> +    (source (origin
>>>> +              (method git-fetch)
>>>> +              (uri (git-reference
>>>> +                    (url "https://github.com/ijp/minikanren.git")
>>>> +                    (commit 
>>>> "10d507785eab30b0f8b47bf8bb37d880731fc031")))
>>> 
>>> Is there no tarball? If possiblem we would prefer this.
>> 
>> No tarball.  I would recommend that the first 7 characters of the
>> commit SHA be used as the package version, and this string here could
>> just be replaced with 'version'.
> 
> Maybe make the version (string-append "0-" commit) so we can eventually
> increment that zero to make upgrades work, as Andreas notes?
> (I think upstream minikanren is frozen anyway.)

Why not use YYYYMMDD.<7-char-sha> so that the version is less arbitrary? 
  It would still sort for upgrades.

Sounds like another set of conventions to document in the manual ;)

-- 
`~Eric

  reply	other threads:[~2015-04-23 19:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 15:15 Add guile-minikanren Christopher Allan Webber
2015-04-23 13:17 ` Andreas Enge
2015-04-23 13:44   ` Taylan Ulrich Bayırlı/Kammer
2015-04-23 13:46   ` Thompson, David
2015-04-23 13:52     ` Andreas Enge
2015-04-23 18:57     ` Ludovic Courtès
2015-04-23 19:48       ` Eric Bavier [this message]
2015-04-23 19:51         ` Andreas Enge
2015-04-23 21:10         ` Ludovic Courtès
2015-04-24  2:46     ` Christopher Allan Webber
2015-04-25 21:30       ` Christopher Allan Webber
2015-04-27  1:46         ` David Thompson

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=5683758a81dab8c8c4a07b4b76944938@openmailbox.org \
    --to=ericbavier@openmailbox.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).