Am Sonntag 14 Juni 2009 10:39:11 schrieb Allan McRae:
This change I am 50/50 on. pkgbase was supposed to be purely informational when splitting packages and it is entirely optional to specify when splitting packages (as pkgname[0] is used as a backup). However, I see that could be useful...
Right, it changes the "only for fancy makepkg output" meaning of pkgbase to a more important role. But as long as this version of makepkg is not released this is possible. Let's say if you split a package you have to define pkgbase and then the same rules apply to it as to pkgname atm. E.g. our tools expect that your PKGBUILD is within a dir with the same name as pkgname. (even though pacman/makepkg does not care about it) But even if we forget about the use for our Arch specific db-scripts its imho very usefull to have some kind of connection between a package and a PKGBUILD. We now have pkgname which is a unique identifier; for split packages that would be pkgbase. PS: We might adjust this patch in a way that pkgbase will only be added for split packages and pkgbase will be required for split packages. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de