Hi, Johannes Winkelmann wrote:
Hi,
On Mon, Jul 28, 2008 at 10:43:50 +0300, Mikhail Kolesnik wrote:
Hi. [...] 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. I'm not using any of the three DE's with a dedicated repository, so I may not know the typical problems here, plus to me there are some questions (see below) which make it hard to judge the different variants.
That said, if I'm looking for a KDE specific app, and there's a dedicated KDE repository, I'd expect it to be there. I'm not sure if any other solution can be considered more intuitive.
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); Not everyone uses contrib either. So if a user is using KDE and the KDE repository, subscribing to contrib for that single KDE app she wants from contrib would be overkill as well.
Maybe would be useful to have a uniq-port-sync-tool
- DE maintainers will be against; Is that really the case?
I have two more questions for DE maintainers which IMO have a major impact on the decision making: a) do you require your repository to be listed before 'opt'? b) do you depend on ports from contrib?
Well, I'm the xfce maintainer, and for what I known I should provide all dependencies which are not listed on core, opt and xorg collections yet. So xfce don't depends on opt or contrib. But for example the xfce terminal depends on 'vte' which is not listed on core/opt/xorg, but its provided by gnome and that implies that I had to duplicated it. Due to that, some collections have to accept duplicates or should exist an extra DE_share_repo for avoiding dups (maybe opt, xorg, xopt, x ?). I also proposed sometimes the repo_depencies concept: (source fragment of 'repoverify') [1] [...] core) REPO_DEPS="core" ;; opt) REPO_DEPS="core opt xorg" ;; xorg) REPO_DEPS="core opt xorg" ;; contrib) REPO_DEPS="core opt xorg contrib" ;; gnome) REPO_DEPS="core opt xorg gnome" ;; kde) REPO_DEPS="core opt xorg kde" ;; xfce) REPO_DEPS="core opt xorg xfce" ;; e17) REPO_DEPS="core opt xorg e17" ;; [...] Best regards, Jose V Beneyto [1]. http://mikeux.dyndns.org/crux/ports/crux-repo-utils/