unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] distro: automake: Update to 1.12.6
Date: Sun, 30 Dec 2012 19:01:51 +0100	[thread overview]
Message-ID: <87han34dww.fsf@gnu.org> (raw)
In-Reply-To: <87r4m7lcav.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sun, 30 Dec 2012 11:44:29 -0500")

Hi,

Nikita Karetnikov <nikita@karetnikov.org> skribis:

> I'm probably missing something, but it seems to me that it's better to
> keep the old recipe instead of replacing it. So it will be possible to
> install different versions (just like with 'nix-env').

It makes sense in some cases, and not in others.

In general, it makes sense to keep several versions for important
components where major versions break compatibility (GCC, Guile, etc.)

For Automake, I don’t think it makes sense, though.  Or did you have
anything special in mind?

> Does Guix support multiple versions?

Well yes, since it’s one directory per package, you can even have
several variants of Automake around, using several variants of Perl.
And you can have your own set of recipes in addition to those that come
with Guix.

Thanks,
Ludo’.

  reply	other threads:[~2012-12-30 18:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22  8:56 [PATCH] distro: automake: Update to 1.12.6 Andreas Enge
2012-12-30 16:24 ` Ludovic Courtès
2012-12-30 16:44   ` Nikita Karetnikov
2012-12-30 18:01     ` Ludovic Courtès [this message]
2013-01-11 16:36       ` Nikita Karetnikov
2013-01-11 17:19         ` Ludovic Courtès
2013-01-03 13:18   ` Andreas Enge
2013-01-03 14:44     ` Ludovic Courtès
2013-01-03 15:24       ` Andreas Enge
2013-01-03 16:04         ` Ludovic Courtès
2013-01-03 16:41           ` Andreas Enge

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=87han34dww.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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).