| 1 |
Brian Harring posted on Sun, 20 Sep 2009 18:17:35 -0700 as excerpted: |
| 2 |
|
| 3 |
> Basically what gain is there? Stabilizing it at this point comes off as |
| 4 |
> "whee, we have py3k stabilized! Now go mask it on all of your boxes |
| 5 |
> since not a lot of the useful things play nice with it right now!" |
| 6 |
|
| 7 |
I'm on ~arch, so dealt with it already, doing pretty much exactly that. |
| 8 |
Nothing I have installed uses py3k yet, and there's really no reason I |
| 9 |
need it installed, so I have it locally masked. |
| 10 |
|
| 11 |
At some point, various packages will begin to depend on it, and when they |
| 12 |
need stabilizing, we'll need py3k stabilized as well. But meanwhile, as |
| 13 |
long as it itself is working well, we can use the time until then to |
| 14 |
smooth the transition when that day arrives, arranging for modules to |
| 15 |
install in multiple slots, etc. |
| 16 |
|
| 17 |
-- |
| 18 |
Duncan - List replies preferred. No HTML msgs. |
| 19 |
"Every nonfree program has a lord, a master -- |
| 20 |
and if you use the program, he is your master." Richard Stallman |
Archives