On Fri, Jan 09, 2009 at 02:52:18PM -0600, Aaron Griffin wrote:
Well, the way the arch SVN repo for build files is organised is by packages, not by repos. That means all community packages will be thrown in together with core, extra, and testing packages.
To get a checkout of community you would have to scan every package directory to see if it's actually in community. I'm not sure if it's possible via standard subversion tools either.
I'm not sure what you mean here. The official repos did away with the "scan all packages" thing a while back. There's no need to regenerate an entire list of all packages, assuming we maintain state properly. Every operation is an add or a remove. We simply use SVN to ensure that the package belongs in that repo.
What I mean is that it doesn't seem like someone could easily checkout the build files for just community packages.
In that case how do you set up permissions properly if trunk build files don't belong to any particular repo? Seems TUs would have access to everything no?