Rox packages make a significant portion of to-be-converted Python package list , and they are maintainer-needed for a long time. How about we lastrite them instead?
Adding bug #512122 because of:
repo.eapi.deprecated rox-base/pager/pager-1.1-r2.ebuild: 1
repo.eapi.deprecated rox-base/rox-clib/rox-clib-2.1.10.ebuild: 1
repo.eapi.deprecated rox-base/tasklist/tasklist-0.5.ebuild: 1
It kinda goes the other way. Cleaning rox kills all the other bugs implicitly :).
Even if you plan to drop support for rox-desktop in the tree, could you plese preserve these ebuilds:
The above ebuilds are relative to the rox-filer file manager, that is used by many on various other desktops environments.
You could as well setup a single ebuild for everyting that is much simpler to maintain.
Well there is no active maintainer for rox, are you're willing to help out here?
(Some of the bugs listed as blockers concern the packages you listed)
If you explain me what I should do I can seriously think about it. I'm no portage expert though, I have some basic knowledge of python but I know little of portage internals (I mean I did manage some local overlay, and that's it).
Some people here are already thinking about volunteering:
If you think I can give a hand with rox I would be glad to maintain some package.
The proxy maintainers procedure is a bit more explained at:
Anyway, I am unsure if would be better to maintain a full desktop in an overlay instead of needing to proxy-maintain all the ebuilds :|
Assuming you want to be the new proxy-maintainer for the packages you mentioned, this is an incomplete list of things, that need to be fixed:
rox-base/rox: check bug #500502 and bug # 309875, update to EAPI5, either maintain rox-extra/videothumbnail, too or remove IUSE="video".
rox-base/rox-lib: migrate from 'python' to 'python-r1 / python-single-r1 / python-any-r1', update to EAPI5.
rox-base/mime-editor: update to EAPI5.
rox-base/thumbs: update to EAPI5.
rox-base/zeroinstall-injector: migrate from 'distutils' to 'distutils-r1'.
rox-extra/archive: update to EAPI5.
In addition to those ebuilds, we have also deprecated eclasses for rox: rox.eclass and rox-0install.eclass.
Thus we need someone who is willing to maintain them, too.
I'll read the documentation, study a bit and I'll try to give you an answer by the end of next week. I'm starting a new work in February and I still don't know how much free time I'll have.
I'm searching for someone to team up with me and divide the maintaining effort (which should be little in the long run, but right now there are lots of things that I have to study, including the EAPI stuff).
If you hear nothing within ten days, it's a no...
Just to be clear, if there are more people wanting to maintain those packages, it's ok for them to work together, as long as someone is around to fix issues :).
If there's only need for rox-filer, I suggest to work on bug #537388 and proxy-maintain this ebuild later.
Updated the rox-filer ebuild. Please check.
OK, is there a quick and dirty way to remove all the rox-related packages (and any stub dependencies they pulled in)? Thanks in advance.
(In reply to Jesse Adelman from comment #12)
> OK, is there a quick and dirty way to remove all the rox-related packages
> (and any stub dependencies they pulled in)? Thanks in advance.
sed -i -e '/^rox/d' /var/lib/portage/world
Categories have been removed.
app-misc/rox-filer has been added to the tree.
See bug #537388