On Wed, 30 Mar 2005 18:53:42 +0100
Oliver Burnett-Hall <[EMAIL PROTECTED]> wrote:

> I think you've misunderstood the proposal/patch; all it means is that if
> the pkgbuild script doesn't define a build() function then the default
> one would be used.
> 
> Personally, I think every pkgbuild script that I've written has had a
> changed build() function, so I'm not sure that this would make much
> difference.
Well, now I got you, there has been some kinda blackout this afternoon :)
Actually, as Jason stated there are plans to for such things, which won't
replace the build function, though instead they provide some useful
functions to stop gconf from updating the database(which needs to
be done on installation not on build) and similar things. If you think
further you will face the situation how should these function provided?
Which package should carry them?
makepkg: nope, cu'z for every new function the pacman package needs to be
         upgraded
gconf itself: very specific and can bring trouble with the dependencies

Current idea is to provide the package groups wise like in gnome-common and
similar. But this isn't thought out completely. 

-tobbi

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to