unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix revisions (Re: [Patch] Tmux Themepack)
Date: Sun, 10 Jul 2016 11:45:20 -0400	[thread overview]
Message-ID: <20160710154520.GA20980@jasmine> (raw)
In-Reply-To: <87lh19zix7.fsf_-_@we.make.ritual.n0.is>

On Sun, Jul 10, 2016 at 02:06:44PM +0000, ng0 wrote:
> A side question: We do guix revisions of packages? I know we had
> a discussion on this in the past which included the string-take
> commit 7 or 8, but even with using grep in the gnu/packages dir
> it's not obvious as egrep -nr 'revision "1"'
> for example just gives 5 results.
> So the documentation needs to be improved, I agree.

Without using a revision integer, `guix package --upgrade` will not work
correctly, since Git hashes do not increase (or decrease) reliably.

For example, the computer can't tell which of these two version strings
is the newer version:

"0.0.0-deadbeef"
"0.0.0-cabba9e"

Not all packages declare a revision variable, but I think it is helpful.

Any suggestions on improving this part of the manual? It *does*
explicity describe this problem and the solution. Should we add the
revision variable to the code example?

  reply	other threads:[~2016-07-10 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 17:23 [Patch] Tmux Themepack Matthew Jordan
2016-06-11  7:45 ` Ricardo Wurmus
2016-06-12 20:01   ` Matthew Jordan
2016-06-18  0:00     ` Leo Famulari
2016-07-10 13:26       ` Matthew Jordan
2016-07-10 16:19         ` Leo Famulari
2016-07-10 17:56           ` Matthew Jordan
2016-07-11  8:41           ` Alex Kost
2016-07-10 14:06       ` guix revisions (Re: [Patch] Tmux Themepack) ng0
2016-07-10 15:45         ` Leo Famulari [this message]
2016-07-10 16:16           ` guix revisions ng0

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=20160710154520.GA20980@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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).