Hello, Alan. On Mon, 28 Jul 2008 10:07:25 -0430 Alan Mizrahi <alan+crux@mizrahi.com.ve> wrote:
This topic sometimes looks hot but is not considered a major issue and nobody has a strong opinion if (and how) it can be solved. Please, follow up with suggestions.
Yes, I don't think its a mayor issue. I don't know about gnome or xfce, but so long I've been asked only once to include a port into the kde repo that used to be in contrib.
Ok, say someone have a digikam port in a personal repo. The list of ports he has to maintain is: digikam, kipi-plugins, libkipi, libkexiv2, libkexif, libkdcraw, jasper. There are more deps found in opt, contrib and (obviously) kde repos. It can't be put in contrib. It is just to much to ask kde maintainer to take it over and test each version upgrade (and it still has deps from contrib). The maintainer is doomed to keep it private forever.
Make a contrib-gnome, contrib-xfce, contrib-kde repos and submit DE specific contrib ports there, adjust rules. cons: - makes things too complicated;
I think this would be by far the best solution. It would keep everybody happy, and people don't have to subscribe to DE specific contrib ports if they just want their basic DE.
I don't see why it has to be more complicated than contrib itself, the rules should be pretty much the same, and whenever someone is given access to contrib he should also be given access to contrib-* (no need to apply to different contrib repos separately).
Not the worst case, but this requires some sort of cooperation with DE maintainers. "Please add this and that option" or "give me that port, I'll maintain it in contrib-foo as it is essential for the app bar". -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta