On Sun, 2007-09-02 at 01:00 +0200, Damir Perisa wrote:

great job!

Sunday 02 September 2007, Jan de Groot wrote: | - make all build() functions the same

by the way: can we not have a predefined function that is defined somewhere central and makepkg knows about? something like buildperl() that you can just run in PKGBUILD if it is the same for a lot of pkgs.

- D

Besides the directory to go to for the build, there's not much difference. Some packages are a bit harder to do because they need customization (some of them have interactivity which you must disable...). I see we have several things going on in our distribution: - universal installed binaries, like gconfpkg in the gconf package to handle postinstall/preremove of gconf schemas - copy&paste like we always do - one stupid file that is copied into many directories because our packages should be able to build on its own (goodconf, badconf, uglyconf in gstreamer). I would love to see this one solved the same way as GConf BTW, a scriptlet in the Gstreamer0.10 package. We should have a unified way of doing these things. Frugalware can do it with their F* macros, Debian can do it with dh_*, Gentoo has their Eclasses, why can't we do this?

Doesn't xterminus have a perl build system chugging along pretty well for a while now? Automated and everything? Wonder what he is up to lately....

2007/9/2, Aaron Griffin :

On 9/1/07, Jan de Groot wrote:

...

We should have a unified way of doing these things. Frugalware can do it with their F* macros, Debian can do it with dh_*, Gentoo has their Eclasses, why can't we do this?

Because everyone passes the buck and wants everyone else to implement their ideas?

Go ahead and do it. Make a script, I'm sure we could figure out some way to get it into things elegantly... like say: /etc/makepkg.d/perl Then have makepkg load that somehow.

/me shrugs

I disagree with this sort of stuff, so I would never do it, and I'm sure a handful of other people feel the same - but if you do it, and it breaks nothing, I see no reason why we couldn't integrate it.

You can send patches to Dan or I

I do like gconfpkg. It greatly simplifies creation of PKGBUILDs for Gnome applications. It is included in gconf package for 2 months already, so I think AUR packages can start using it. The good thing is that solution like gconfpkg doesn't require any changes to Pacman. The bad thing is that this solution can be used only for packages that depend on a package which include such script. -- Roman Kyrylych (Роман Кирилич)