From: Ricardo Wurmus <rekado@elephly.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: Guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: installing python 2 and python 3 in the same profile
Date: Mon, 12 Mar 2018 09:37:25 +0100 [thread overview]
Message-ID: <87y3ixsn96.fsf@elephly.net> (raw)
In-Reply-To: <m1k1uhn55c.fsf@ordinateur-de-catherine--konrad.home>
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> It is an unnecessary restriction to *prevent* users from installing
>> Python 2 and 3 interpreters into the same profile. Any errors we see
>
> I agree. But the current question is not if we should allow people to
> shoot themselves into the foot, but how much effort we should invest to
> make this possible.
It hasn’t always been like this. We added a feature to anticipate
conflicts that would happen at the time a profile is built. This
feature now prevents you from installing variants of the same package
into the same profile — this is what we want. Python 2 and 3 are not
variants of the same package, so preventing their installation into the
same profile is a bug introduced by that new feature.
My proposal would require very little effort to implement. It is just a
question of whether there is a more elegant approach.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-03-12 8:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 7:50 installing python 2 and python 3 in the same profile Ricardo Wurmus
2018-03-10 8:34 ` Pjotr Prins
2018-03-11 9:11 ` Konrad Hinsen
2018-03-11 11:10 ` Ricardo Wurmus
2018-03-11 12:42 ` Pjotr Prins
2018-03-11 13:30 ` Hartmut Goebel
2018-03-11 13:36 ` Pjotr Prins
2018-03-12 7:07 ` Konrad Hinsen
2018-03-12 8:37 ` Ricardo Wurmus [this message]
2018-03-11 13:00 ` Hartmut Goebel
2018-03-11 13:27 ` Pjotr Prins
2018-03-13 21:52 ` Ludovic Courtès
2018-03-14 8:40 ` Ricardo Wurmus
2018-03-14 11:39 ` Hartmut Goebel
2018-03-14 14:30 ` Konrad Hinsen
2018-03-15 9:11 ` Ludovic Courtès
2018-03-15 9:37 ` Konrad Hinsen
2018-03-16 20:59 ` Ricardo Wurmus
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=87y3ixsn96.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.