On Wednesday 28 September 2005 03:18, Mark Rosenstand wrote: > 4. Declaration of post_install() and friends inside PKGBUILDs. > > It seems silly that you're declaring a build() function but need an > external file to declare other basic functions. I do realize that it's > easier to include the file with install time functions in the tarball, but > it shouldn't be too hard to extract them from the PKGBUILD and then > include.
I was reading yesterday the steps required to make a RPM. I've also noticed that the RPMs (at least the OpenSUSE RPMs) have all the functions declared into one file (I think it's called the spec file). I've asked myself the exact same thing then. The only reason I could find was that, because of a bash-script thing, you must write all the functions, even if they're empty. Also, maybe if the install file is not included, something else is used as default. I believe the spec file used by the RPM build tool is interpreted and afterwards it is processed (the file doesn't have a format I've seen anywhere else). PKGBUILDS are directly processed as bash scripts. Mircea /IceRAM P.S. Oh yeah, building RPMs is WAY MORE DIFFICULT than making an Arch package - lots of tools required.. lots of steps... -- Psi Forums Moderator/Bug Tracker Manager Psi Windows Installer Maintainer/ArchLinux Package Maintainer http://mircea.bardac.net
pgpMNg0ktekLH.pgp
Description: PGP signature
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
