Hi. 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. I guess you are familiar with current contrib rules [1]. The problem: an average CRUX contributor can't just put a port depending on something from gnome/kde/xfce (DE) into contrib, nor can he put it into the specific DE repository. It makes many ports hard to find/update/trust. Some ports will die inside private repos, as not many users like to subscribe to those (and play with prt-get.conf to build their personal dependency strategy). While I admit CRUX is DIY distro without a strict policy for everything... the status and possible usage scenarios (tips) of DE repositories looks unintuitive. Another aspect is a so called 'port duplication' issue. In general, it might be not fatal to have ports with different options in different repos. One will just have to put his favourite DE on the top of prt-get.conf/prtdir statements. It might work in most cases, but we have to be aware of the potential problems in each specific case. Few possible ways to go: Pretend that DE repos are just a part of contrib (and modify rules). cons: - DE maintainers might not like generic contrib rules or just to be a part of it; Give contrib members the power to submit ports to DE repos (insist on cooperation). cons: - not everyone even use those DE (subscribing to everything is an overkill); - DE maintainers will be against; Make a contrib-gnome, contrib-xfce, contrib-kde repos and submit DE specific contrib ports there, adjust rules. cons: - makes things too complicated; Port duplication (at least with opt) seems hard to overcame in any case. It could be possible to clean up contrib and DE repos of the ports that are in opt to some extent. [1] http://crux.nu/Main/ContribRules -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta