From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: Different versions of a package in the same profile?
Date: Sat, 1 Nov 2014 11:46:10 +0100 [thread overview]
Message-ID: <20141101104610.GC31318@debian> (raw)
In-Reply-To: <87lhnxgnrx.fsf_-_@gnu.org>
On Fri, Oct 31, 2014 at 12:07:14AM +0100, Ludovic Courtès wrote:
> Technically it would be easy to allow the installation of different
> versions of a package in the same profile, but I wonder about the
> implications.
>
> For instance, ‘-u foo’ would upgrade all the installed versions of
> ‘foo’, so you would end up with exactly the same version twice.
Good catch (or rather "bad feature"?).
So should we indeed rename version 2 of the python package to python2, to
allow easy installation together with python version 3?
We could do the same for Qt, but if anyway versions 4 and 5 are not
installable together, there does not seem to be a need.
How about guile?
In any case, the outcome of installation should not depend on whether we
do them in one or in several commands.
Another idea: How about letting "guix package -u foo" upgrade only the
package with name foo and the latest version if there are several with the
same name?
Andreas
next prev parent reply other threads:[~2014-11-01 10:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 17:30 Problems with downloading from https Alex Kost
2014-10-25 20:02 ` Ian Denhardt
2014-10-26 7:03 ` Alex Kost
2014-10-26 13:46 ` Ludovic Courtès
2014-10-26 19:35 ` Alex Kost
2014-10-26 21:01 ` Ludovic Courtès
2014-10-27 9:06 ` Mark H Weaver
2014-10-27 12:24 ` Ludovic Courtès
2014-10-27 12:44 ` Ludovic Courtès
2014-10-27 13:27 ` Alex Kost
2014-10-27 14:43 ` Mark H Weaver
2014-10-27 16:24 ` Ludovic Courtès
2014-10-27 16:44 ` Alex Kost
2014-10-28 8:03 ` Ludovic Courtès
2014-10-29 22:22 ` Andreas Enge
2014-10-30 7:27 ` Alex Kost
2014-10-30 7:49 ` Andreas Enge
2014-10-30 12:31 ` Alex Kost
2014-10-30 12:38 ` Andreas Enge
2014-10-30 19:30 ` Alex Kost
2014-10-30 23:07 ` Different versions of a package in the same profile? Ludovic Courtès
2014-11-01 10:46 ` Andreas Enge [this message]
2014-11-02 17:22 ` Ludovic Courtès
2014-11-02 17:39 ` Andreas Enge
2014-10-30 13:20 ` Problems with downloading from https Ludovic Courtès
2014-10-30 17:05 ` Ian Denhardt
2014-10-30 19:08 ` Alex Kost
2014-10-31 4:54 ` Ian Denhardt
2014-10-30 14:48 ` Ludovic Courtès
2014-10-27 13:01 ` Alex Kost
2014-10-27 14:32 ` Mark H Weaver
2014-10-25 21:53 ` Ludovic Courtès
2014-10-26 5:30 ` [PATCH 0/1] " Ian Denhardt
2014-10-26 5:21 ` [PATCH 1/1] README: add a note about optional GnuTLS dependency Ian Denhardt
2014-10-27 12:54 ` Ludovic Courtès
2014-10-27 10:49 ` [PATCH 0/1] Re: Problems with downloading from https Ian Denhardt
-- strict thread matches above, loose matches on Subject: below --
2014-11-02 18:52 Different versions of a package in the same profile? Federico Beffa
2014-11-03 8:58 ` Ludovic Courtès
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=20141101104610.GC31318@debian \
--to=andreas@enge.fr \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).