unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Philippe Veber <philippe.veber@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: List available versions of package.
Date: Sun, 23 Jun 2019 00:46:35 +0200	[thread overview]
Message-ID: <87a7e9tf04.fsf@elephly.net> (raw)
In-Reply-To: <CAOOOohRr08ODzSZi6hzo_4=UMCr1+di8mxOF3bEq7D+79cp6xA@mail.gmail.com>


Hi Philippe,

> Also, is it expected that packages from guix commits dating
> from a few years ago will still work in this setting? Thanks!

Commits before the introduction of inferiors likely won’t work,
unfortunately.

For running old versions I recommend writing new package variants
instead and including them in a channel.  Using inferiors is a good idea
when you want to reproduce a Guix environment that somebody else (or
your younger self) recorded, but I would not recommend them as a way to
make past software variants available.  If you are not interested in a
particular old state of the world but only care about a particular
version of a single piece of software (that may be built with current
toolchains and libraries) then package variants are a better idea.

For bioinfo package variants also take a look at the guix-bimsb channel:

    https://github.com/BIMSBbioinfo/guix-bimsb

(I should update the README to recommend using channels instead of
GUIX_PACKAGE_PATH…)

--
Ricardo

  parent reply	other threads:[~2019-06-22 22:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 18:27 List available versions of package Philippe Veber
2019-06-10 21:31 ` Tobias Geerinckx-Rice
2019-06-11  7:43   ` Philippe Veber
2019-06-22 11:26     ` Philippe Veber
2019-06-22 19:08       ` Tobias Geerinckx-Rice
2019-06-26 18:32         ` Philippe Veber
2019-06-22 22:46       ` Ricardo Wurmus [this message]
2019-06-26 18:43         ` Philippe Veber
2019-06-26 20:25           ` Ricardo Wurmus
2019-06-30 11:50             ` Philippe Veber
2019-07-02 15:48         ` Leo Famulari

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=87a7e9tf04.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=philippe.veber@gmail.com \
    /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).