On 10/29/07, Jason Chu <jason@archlinux.org> wrote:
And it helps to treat package repositories as branches... though... how do you know what PKGBUILD to use for a repository other than core/extra? There's a test_kernel24, test_kernel, and test_udev. Each of them have different versions of kernel24, kernel, and udev.
In the svn suggestion, we're explicit about which version is in testing, how would we figure it out in git?
The intent is to actually have two different versions. If 'test_kernel' and 'test_udev' spawned off their own mini-repos, each would have a kernel24. They would need to be merged to the master branch later. When Dan and I talked about this, the whole purpose was experimental features and/or rebuilds. Here's a use-case: Paul makes his AUFS changes to the kernel on a test_aufs branch (which may include the aufs and aufs-utils packages too). This allows the normal kernel to continue on as planned. People test it, everyone likes it, changes get rebased a few times, and eventually merged to master.