On 04/06/2008, at 10:15 PM, Antonio Huete Jimenez wrote:
The only remaining thing I could just figure out is to use git to manage the ABS tree, generate branches for every OS it's being ported, and provide monthly sets of patches providing OS specific changes that don't affect ArchLinux at all (and AL devel don't have to take any action on them if they don't want).
All this monthly set patches can be managed with tags.
I really don't see the point of branching the Archlinux ABS tree. It's the Archlinux ABS tree, not some generic ABS tree that's supposed to work for everything. More importantly it's a set of PKGBUILDs for a Linux system. BSD isn't Linux, and although some of the userland is similar, a lot of it is not. Somewhere along the line there will be more differences than similarities in the PKGBUILDs, and imo, it's just easier to copy the Archilnux ABS tree and work off that. Now a generic set of PKGBUILDs for the BSD system may be a good idea. They would definitely have more similarities than ones from a Linux system. Also I just want to make clear that the ABS tree is separate from the makepkg and pacman projects.