| 1 |
commit: c1c1bf36d6920e0d0bf45d0aa308e539fb81cdc7 |
| 2 |
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Wed Dec 16 17:31:10 2015 +0000 |
| 4 |
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Wed Dec 16 17:31:10 2015 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=c1c1bf36 |
| 7 |
|
| 8 |
Remove 2012-11-06-PYTHON_TARGETS-deployment |
| 9 |
|
| 10 |
.../2012-11-06-PYTHON_TARGETS-deployment.en.txt | 41 ---------------------- |
| 11 |
...2012-11-06-PYTHON_TARGETS-deployment.en.txt.asc | 9 ----- |
| 12 |
2 files changed, 50 deletions(-) |
| 13 |
|
| 14 |
diff --git a/2012-11-06-PYTHON_TARGETS-deployment/2012-11-06-PYTHON_TARGETS-deployment.en.txt b/2012-11-06-PYTHON_TARGETS-deployment/2012-11-06-PYTHON_TARGETS-deployment.en.txt |
| 15 |
deleted file mode 100644 |
| 16 |
index 0498ff0..0000000 |
| 17 |
--- a/2012-11-06-PYTHON_TARGETS-deployment/2012-11-06-PYTHON_TARGETS-deployment.en.txt |
| 18 |
+++ /dev/null |
| 19 |
@@ -1,41 +0,0 @@ |
| 20 |
-Title: PYTHON_TARGETS deployment |
| 21 |
-Author: Michał Górny <mgorny@g.o> |
| 22 |
-Content-Type: text/plain |
| 23 |
-Posted: 2012-11-06 |
| 24 |
-Revision: 1 |
| 25 |
-News-Item-Format: 1.0 |
| 26 |
- |
| 27 |
-Recently, a few new Python eclasses have been deployed. As ebuilds |
| 28 |
-migrate, the way they support multiple Python implementations will |
| 29 |
-change. The previous method built Python modules for Python |
| 30 |
-implementations selected through `eselect python'. The new method uses |
| 31 |
-the PYTHON_TARGETS USE flags to explicitly name the implementations the |
| 32 |
-modules shall be built for. |
| 33 |
- |
| 34 |
-If you are running a modern system with only Python 2.7 & 3.2 installed, |
| 35 |
-then you don't have to do anything. The defaults will simply fit you, |
| 36 |
-and let you keep your system up-to-date when new Python versions are |
| 37 |
-deployed. |
| 38 |
- |
| 39 |
-However, if you'd like to use another set of Python implementations, you |
| 40 |
-will need to set PYTHON_TARGETS in your make.conf file appropriately. |
| 41 |
-This variable names the enabled implementations in the standard way |
| 42 |
-common to all USE_EXPAND variables. |
| 43 |
- |
| 44 |
-For example, a setup enabling all major Python implementations would |
| 45 |
-look like: |
| 46 |
- |
| 47 |
- PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5" |
| 48 |
- |
| 49 |
-The variable should list all Python implementations which are going to |
| 50 |
-be used on the system; missing a particular value there will result |
| 51 |
-in missing Python modules. |
| 52 |
- |
| 53 |
-A complete list of all possible values can be obtained using a command |
| 54 |
-equivalent to the following: |
| 55 |
- |
| 56 |
- emerge -1pv dev-python/python-exec |
| 57 |
- |
| 58 |
-For more details, please see the python-r1 User's Guide [1]. |
| 59 |
- |
| 60 |
-[1] http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml |
| 61 |
|
| 62 |
diff --git a/2012-11-06-PYTHON_TARGETS-deployment/2012-11-06-PYTHON_TARGETS-deployment.en.txt.asc b/2012-11-06-PYTHON_TARGETS-deployment/2012-11-06-PYTHON_TARGETS-deployment.en.txt.asc |
| 63 |
deleted file mode 100644 |
| 64 |
index e424445..0000000 |
| 65 |
--- a/2012-11-06-PYTHON_TARGETS-deployment/2012-11-06-PYTHON_TARGETS-deployment.en.txt.asc |
| 66 |
+++ /dev/null |
| 67 |
@@ -1,9 +0,0 @@ |
| 68 |
------BEGIN PGP SIGNATURE----- |
| 69 |
-Version: GnuPG v2.0.19 (GNU/Linux) |
| 70 |
- |
| 71 |
-iJwEAAEIAAYFAlCZfWgACgkQfXuS5UK5QB2CpwQAhw8AxBJmy/ZUWxRfEfzTbpfH |
| 72 |
-5cYRmkBMDPpmg6Y3GhqPhM3SAGg+blBgrHAg+VUSzBlTdCEEQPdz8+Pm+TVCUgnS |
| 73 |
-FnnXlxc+V83ylJSY1do9Dqo2hVo+jQescJIKznMbaLAFVXCLAIvVMunl3oLYkFG2 |
| 74 |
-OFOjS+x1M7AytNVNo3g= |
| 75 |
-=KRsI |
| 76 |
------END PGP SIGNATURE----- |
Archives