Gentoo Archives: gentoo-scm

From: Ryan Hill <dirtyepic@g.o>
To: gentoo-scm@l.g.o
Subject: Re: [gentoo-scm] Splitting gentoo-x86 repository for easier consumption
Date: Sat, 11 Apr 2009 18:48:21
Message-Id: 20090411124958.5c14c46c@halo.dirtyepic.sk.ca
In Reply to: [gentoo-scm] Splitting gentoo-x86 repository for easier consumption by Maciej Mrozowski
On Sat, 11 Apr 2009 14:40:27 +0200
Maciej Mrozowski <reavertm@××××××.fm> wrote:

> Let's look at tree - one thing can be said about each package - it belongs to > some herd or (doesn't, and it's with status maintainer wanted or maintained by > individual developers). > So creating separate repository for each herd is the most obvious (and naive) > idea.
While this may seem like a good idea for those projects and herds that are well defined, well-oiled machines, I can count the number of these projects in Gentoo on one hand.
> Pros are the following: > - project members taking care of some herd (or belonging to herd?) receive > (and have access) (only) to repository they are interested in, resulting in > smaller pulls/pushes
...and isolating them from the rest of the tree, as well as the rest of developers from them.
> - some level of isolation - gives possibility to restrict access (for example: > "only toolchain and arch teams allowed here")
This is counter to the ideals behind Gentoo, blah blah. In reality, if someone screws up toolchain stuff, they only do it once.
> - profile can be (should be actually) separated in another repository and > developed easier
Repositories, when split, are best split into atomic units. Separating profiles from packages, given their dependence on each other, is a non-starter. I'm not sure what we'd do with eclasses either. Obviously they can't be split into herds, but they need to be updated with the ebuilds themselves. In Gentoo development the atomic unit is the repo itself, for better or worse.
> Some cons: > - projects are now more dependant on other projects and its responsiveness, > unless access is granted to all repositories for every developer
Which is one of the biggest problems we already have IMHO.
> - not settled yet what to do with orphaned/proxy maintained packages and herd- > switching
We have ~800 maintainer-needed packages right now. We have multitudes more that belong to herds with no real people in them, or have unresponsive maintainers. Cutting them off from the rest of the tree by making them harder to get to isn't going to improve things. -- gcc-porting, by design, by neglect treecleaner, for a fact or just for effect wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

Attachments

File name MIME type
signature.asc application/pgp-signature