1 |
Dale posted on Sun, 02 Oct 2011 06:49:04 -0500 as excerpted: |
2 |
|
3 |
> I know the KDE3 folks subscribe here and wanted to let you know about |
4 |
> this. I got this after I done my sync: |
5 |
> |
6 |
> Building database (/var/cache/eix) .. |
7 |
|
8 |
> [1] "kde-sunset" /var/lib/layman/kde-sunset (cache: |
9 |
> parse|ebuild*#metadata-flat#assign) |
10 |
> Reading category 17|155 ( 10%): app-misc .. * |
11 |
> * |
12 |
> "/var/lib/layman/kde-sunset/app-misc/releaseforge/ |
13 |
releaseforge-1.3.ebuild": |
14 |
> * Deprecation Warning: Usage of distutils.eclass in packages not |
15 |
> supporting installation |
16 |
> * for multiple Python ABIs in EAPI <=2 is deprecated and will be |
17 |
> banned on 2011-06-01. |
18 |
|
19 |
The short version of the story is that there have been some changes and |
20 |
that message can be ignored, for now. |
21 |
|
22 |
The longer version... well, let's say that a certain former gentoo/python |
23 |
project dev is just that, former, and that the disruptively high rate of |
24 |
python eclass code churn and function deprecation and removal has slowed |
25 |
WAAAYYY down. It'll probably pick back up slightly as others pick up the |
26 |
pieces and development gets back to normal, but it should remain far more |
27 |
modest and less disruptive than it was, as that wasn't normal (or, it |
28 |
turns out, acceptable for the rest of gentoo) either. |
29 |
|
30 |
Similarly, it's rather unlikely that the methods used to stabilize |
31 |
python-3 will be repeated any time soon. (Heh, at least they didn't move |
32 |
python-2 out of the tree to a python-sunset overlay... but the |
33 |
circumstances there are quite different as unlike kde/qt, upstream python |
34 |
continues to support python-2, and unlike python, not so much of the rest |
35 |
of the tree is so widely affected by kde. The kde thing was more |
36 |
upstream policy, the python thing more a gentoo-only thing.) |
37 |
|
38 |
That's why the named date has passed without any action, but the warning |
39 |
remains. Everything's more or less frozen in place as the folks picking |
40 |
up the pieces assess the situation and decide where to go from here. |
41 |
From what I've read, many of the changes have already been done in the |
42 |
python overlay, and they have to figure out whether to move them to the |
43 |
tree, but slower, or to revert them in the python overlay, or if a |
44 |
different solution needs to be worked out and tested in the python |
45 |
overlay, before moving to the tree. |
46 |
|
47 |
(FWIW, I believe said developer remains active in the python overlay, |
48 |
helping to straighten things out or at least explain where he was going |
49 |
with the changes so what to do with them can be better worked out, and he |
50 |
does still post to gentoo-dev occasionally, of course now without a gentoo |
51 |
address, so he's still active in the community and I guess helping to |
52 |
pick up the pieces. What happens from here on out, however, remains to |
53 |
be seen. Maybe he'll return as a dev, having learned his lesson, perhaps |
54 |
he's not even interested, but at least he's still around, so AFAIK |
55 |
there's still some bridges remaining unburned.) |
56 |
|
57 |
So, um, yeah, the deprecation message can be ignored for now. It'll |
58 |
probably be removed at some point. If they do decide to kill that |
59 |
functionality, etc, expect some further warning and likely discussion on |
60 |
the dev list (which I know both you and I follow) first. |
61 |
|
62 |
-- |
63 |
Duncan - List replies preferred. No HTML msgs. |
64 |
"Every nonfree program has a lord, a master -- |
65 |
and if you use the program, he is your master." Richard Stallman |