all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Matthew Jordan <matthewjordandevops@yandex.com>,
	Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [Patch] ruby-byebug@9.0.5
Date: Wed, 8 Jun 2016 22:41:03 +1000	[thread overview]
Message-ID: <5758125F.6030401@uq.edu.au> (raw)
In-Reply-To: <874m97gv39.fsf@mailerver.i-did-not-set--mail-host-address--so-tickle-me>



On 06/06/16 07:54, 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 are some examples of multiple versions being included in Guix e.g. 
Ruby itself, GCC, etc, and we do tend to more commonly keep multiple 
versions of compilers and runtime environments.

> Although I have not submitted them yet.

Good luck. there are others working on node you may be able to 
coordinate with.

Thanks,
ben

  reply	other threads:[~2016-06-08 12:41 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 [this message]
2016-06-10 15:11           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5758125F.6030401@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.