From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Strange python-updater error
Date: Wed, 09 Jun 2010 11:24:16 -0400 [thread overview]
Message-ID: <4C0FB220.4090107@libertytrek.org> (raw)
In-Reply-To: <4C0FAE81.5090006@gmail.com>
On 2010-06-09 11:08 AM, Dale wrote:
> If I recall correctly, there are a few programs that can run with
> python 3. Thing is, there are still a LOT of them that can't run with
> it and must have python 2. If you switch to python 3, you will have a
> mess on your hands. If nothing actually requires python 3, mask it
> for now. It will be a while before you will have to have it anyway.
> When that time comes, portage will tell you that some package that
> must have python 3 only is masked. Then you can remove the mask,
> install it and switch to it.
>
> This is just to save you some "issues" later on. Trying to use python
> 3 right now is not going to work. Wait until things are able to use
> and go through the update process then and only have to do it once.
>
> That's my $0.02 worth.
So... for those of use who have already installed it (and thankfully I
did actually read the notes about not switching to it), should me
uninstall it then mask it? Or just leave it alone? I'm guessing it won't
hurt anything, again as long as I don't stupidly switch to it?
next prev parent reply other threads:[~2010-06-09 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 10:32 [gentoo-user] Strange python-updater error Jacques Montier
2010-06-09 13:17 ` [gentoo-user] " walt
2010-06-09 13:47 ` Jacques Montier
2010-06-09 14:26 ` Dale
2010-06-09 14:33 ` Jacques Montier
2010-06-09 15:08 ` Dale
2010-06-09 15:24 ` Tanstaafl [this message]
2010-06-09 16:21 ` Alex Schuster
2010-06-09 16:28 ` Neil Bothwick
2010-06-09 16:50 ` Tanstaafl
2010-06-10 5:36 ` Dale
2010-06-10 10:24 ` Sebastian Beßler
2010-06-10 17:11 ` Dale
2010-06-09 13:33 ` [gentoo-user] " Neil Bothwick
2010-06-09 15:07 ` Jacques Montier
2010-06-09 17:24 ` Sebastian Beßler
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=4C0FB220.4090107@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox