From: Ralph Seichter <m16+gentoo@monksofcool.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python 3.6
Date: Thu, 28 Jun 2018 00:37:13 +0200 [thread overview]
Message-ID: <81f0d6c7-5927-e240-e2f3-679b87f7b18e@monksofcool.net> (raw)
In-Reply-To: <m3lgazeuxz.wl-covici@ccs.covici.com>
On 28.06.18 00:16, John Covici wrote:
> after doing a world update, there are still packages which apparently
> need both 3.4 and 3.5, so I cannot remove them.
That sounds like you might still have some packages where the use flags
python_targets_python3_4 and/or python_targets_python3_5 are active. Vim
comes to my mind as an example:
# equery u app-editors/vim
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for app-editors/vim-8.0.1298:
U I
( ... )
- - perl : Add optional support/bindings for the Perl language
- - python : Add optional support/bindings for the Python language
- - python_single_target_python2_7 : Build for Python 2.7 only
- - python_single_target_python3_4 : Build for Python 3.4 only
- - python_single_target_python3_5 : Build for Python 3.5 only
+ + python_single_target_python3_6 : Build for Python 3.6 only
+ + python_targets_python2_7 : Build with Python 2.7
- - python_targets_python3_4 : Build with Python 3.4
- - python_targets_python3_5 : Build with Python 3.5
+ + python_targets_python3_6 : Build with Python 3.6
- - racket : Enable support for Scheme using dev-scheme/racket
( ... )
As you can see, vim was built with support for Python 2.7 and 3.6, but
neither 3.4 nor 3.5. Which is the way I want it.
-Ralph
next prev parent reply other threads:[~2018-06-27 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 20:43 [gentoo-user] python 3.6 Bill Kenworthy
2018-06-27 21:04 ` Ralph Seichter
2018-06-27 22:16 ` John Covici
2018-06-27 22:36 ` Bill Kenworthy
2018-06-28 7:00 ` Marc Joliet
2018-06-27 22:37 ` Ralph Seichter [this message]
2018-06-27 23:28 ` Neil Bothwick
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=81f0d6c7-5927-e240-e2f3-679b87f7b18e@monksofcool.net \
--to=m16+gentoo@monksofcool.net \
--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