On Jan 4, 2008 9:11 AM, Travis Willard <travis@archlinux.org> wrote:
Hey guys,
With ABS splitting off from pacman, I was wondering where makeworld and the .proto files belonged.
To me, makeworld seems to be an abs tool (and even mentions ABS in its usage) so it would seem to belong in the abs project, not with pacman itself.
Big +1 here. I have been slowly but surely trying to eliminate the hard links to ABS in the pacman source, and this is (as far as I know) the last one, although we could generalize it. I can offer assistance here getting it moved over and cleaned up (remove the gettext stuff?) if you want, as I've already had to do this with the abs script.
The proto files (PKGBUILD.proto, install.proto, and possibly a ChangeLog.proto?) seem to belong with makepkg in my mind. Any changes in these proto files would be directly caused by changes to makepkg, and the coupling of putting them in with the pacman package seems to make sense. I've never understood why we sync them with abs in the first place - if someone wants a prototype PKGBUILD to start from, why should they have to download the entirety of our repos' build scripts?
Original decisions die hard :). Take a glance at contrib/ in the pacman source- there you will find PKGBUILD.proto and proto.install, which should always be the canonical definition. I think it would be very wise for us to install these with the pacman package somewhere in /usr/share, and maybe have some symlinks for old times sake in the abs package from /var/abs/. Note to self: look into where those files should live in the pacman-git repo (probably should be somewhere besides contrib as they should be installed by default).
In short, I think we should move makeworld to the abs project/package, and move the prototype files into the pacman project/package, perhaps in /usr/share/pacman/*proto?
Thoughts?
Good to see you already taking charge. Thanks! -Dan