unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Matthew Jordan <matthewjordandevops@yandex.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [Patch] ruby-byebug@9.0.5
Date: Fri, 10 Jun 2016 11:11:24 -0400	[thread overview]
Message-ID: <20160610151124.GA29071@jasmine> (raw)
In-Reply-To: <874m97gv39.fsf@mailerver.i-did-not-set--mail-host-address--so-tickle-me>

On Sun, Jun 05, 2016 at 05:54:34PM -0400, Matthew Jordan wrote:
> 
> > In general, Guix handles this just fine. But somebody has to maintain
> > all those versions ;) We often suggest that if one user needs some old
> > version of a package, they maintain the package privately. For example,
> > using $GUIX_PACKAGE_PATH.
> 
> Ah okay, that makes sense. Does this also also apply to compilers and
> runtime environments? As I have two pachtes for the current versions of
> node (JavaScript runtime), one is the reccomended version and the other
> represents the latest stable version.

There's no hard rule that allows us to keep multiple versions of
compilers and runtimes. I think we keep those around for a variety of
reasons: bootstrapping chains; many packages still require the old
version; it was very difficult to make the package work so it's not
reasonable to ask users to recreate and maintain the old versions
themselves; etc.

      parent reply	other threads:[~2016-06-10 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 15:38 [Patch] ruby-byebug@9.0.5 Matthew Jordan
2016-06-02 10:19 ` Ben Woodcroft
2016-06-02 12:19   ` Ben Woodcroft
2016-06-05 21:22     ` Matthew Jordan
2016-06-05 21:43       ` Leo Famulari
2016-06-05 21:54         ` Matthew Jordan
2016-06-08 12:41           ` Ben Woodcroft
2016-06-10 15:11           ` Leo Famulari [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=20160610151124.GA29071@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=matthewjordandevops@yandex.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.
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).