Time to go.
Reminder: also dev-python/wxpython-docs.
This is now holding up libpng15 per se, like a real bottleneck so don't be suprised to see this getting p.masked (likely today) with remaining revdeps.
Do it.
These need dev-python/wxpython-2.6: =app-dicts/opendict-0.6.1 =dev-python/pythoncard-0.8.2 =dev-python/python-dsv-1.4.0-r1 =dev-util/boa-constructor-0.6.1 =games-action/xpilot-ng-4.7.3 =games-puzzle/londonlaw-0.2.1-r2 =media-video/tovid-0.31-r2 =net-ftp/ftpcube-0.5.1* (p.masked already) =net-p2p/bittornado/bittornado-0.3.18-r2 This one needs x11-libs/wxGTK-2.6: =dev-games/crystalspace-1.2.1
And scratch that libpng15 thing, I've fixed 2.6 instead, was less work to push at once. I will help however getting this done after I'm done with libpng15. ;-)
Thanks. I knew there were more hiding somewhere. I finally finished the project that's been killing me at work today so I should have more time to work on Gentoo soon.
These left: =dev-python/pythoncard-0.8.2 =dev-python/python-dsv-1.4.0-r1 =dev-util/boa-constructor-0.6.1 =games-action/xpilot-ng-4.7.3 (already masked) =games-puzzle/londonlaw-0.2.1-r2 (already masked) =media-video/tovid-0.31-r2 =net-p2p/bittornado/bittornado-0.3.18-r2
These left: =dev-python/pythoncard-0.8.2 (this one is masked) =dev-python/python-dsv-1.4.0-r1 =dev-util/boa-constructor-0.6.1 =media-video/tovid-0.31-r2 =net-p2p/bittornado/bittornado-0.3.18-r2
These left: =dev-python/pythoncard-0.8.2 (masked, lastrited) =dev-util/boa-constructor-0.6.1 (masked, lastrited) So only these 2 needs looking into far as I can see: =media-video/tovid-0.31-r2 =net-p2p/bittornado/bittornado-0.3.18-r2
I didn't see any explanation for removal. I'm not questioning the decision, but I'd like to learn more about why the decision was made. Thanks. Questions: 1. Why are wxGTK-2.6 and wxpython-2.6 being removed? Is there some discussion I can read to learn more about this? 2. Have the masked packages been tested for upward compatibility with wxGTK-2.8 and wxpython-2.8? Is there some discussion I can read to learn more about this? 3. Have any less disruptive options been considered? Is there some discussion I can read to learn more about this?
> Questions: > 1. Why are wxGTK-2.6 and wxpython-2.6 being removed? Is there some discussion I > can read to learn more about this? Because I'm the maintainer and I don't want to maintain them any more. > 2. Have the masked packages been tested for upward compatibility with wxGTK-2.8 > and wxpython-2.8? Yes. > 3. Have any less disruptive options been considered? The goal is removal. I'm not sure how that could be made less disruptive. Samuli: bittornado can go. i wanted to keep pythoncard but they haven't released 1.0 and the last mention of it was May so let's drop it.
nothing could have made more "less distruptive" except by actually porting some of the masked/removed packages to wx 2.8 myself or using unreleased code from repositories not touched for months, if not years so sorry for inconvinience (which package are you talking about btw?)
(In reply to comments #11 and #12) > Because I'm the maintainer and I don't want to maintain them any more. No offense was intended. I'm sorry if I gave a different impression. Ryan, couldn't you just say that 2.6 is unmaintained and leave the dependent packages? Samuli, maybe someone else will decide to port them to 2.8.
(In reply to comment #13) > Samuli, maybe someone else will decide to port them to 2.8. That is fine up until a point, and we are long past that point. The time has been already given for people to migrate.
(In reply to comment #13) > (In reply to comments #11 and #12) > > Because I'm the maintainer and I don't want to maintain them any more. > > No offense was intended. I'm sorry if I gave a different impression. None taken. > Ryan, couldn't you just say that 2.6 is unmaintained and leave the dependent > packages? No, because it would have been broken already many times over and removed anyways. The latest reason would have been the libpng-1.5 upgrade but there have been several in the last year. The only packages that haven't been migrated since 2.8 was released 5+ years ago are those that were already dead before then. A few didn't even work anymore and no one noticed. You still haven't said what package you want to keep around. We can take another look at it.
(In reply to comment #15) > You still haven't said what package you want to keep around. We can take > another look at it. The one I'm interested in is pythoncard. I'll try to build it with the 2.8 versions and see how much needs to be fixed. I've always wanted to play with it. This gives me some incentive.
Could net-p2p/bittornado be kept for its non-GUI parts, such as the 'bttrack' program? It only depends on wxpython if built with the "gtk" USE-flag.
Sure. Open up a new bug for it and I'll take care of it.
(In reply to comment #18) > Sure. Open up a new bug for it and I'll take care of it. Bug 391685. Thanks!
Now removed. Closing.
