On Mon, Feb 23, 2009 at 4:56 PM, Allan McRae <allan@archlinux.org> wrote:
Aaron Griffin wrote:
On Mon, Feb 23, 2009 at 3:36 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Montag, 23. Februar 2009 22:26:36 schrieb Aaron Griffin:
Or something to that effect, that would not only build all packages in a chroot, but auto-bump the pkgrels and dump the correct results to your svn dir, for a later run of testingpkg...
Would be ncie to have some helper scripts. I use some dumb scripts to manage the kde rebuilds: http://git.archlinux.de/build-scripts/tree/kde
Maybe some of those can be extended to be more genereal. Espeically this which sets pkgver, pkgrel and updates the md5sums: http://git.archlinux.de/build- scripts/tree/kde/update-pkgbuilds (the awk scripts is stolen from some post of the forums ;-))
And I just noticed the undocumented -i flag to makechrootpkg, which installs a package without dirtying the chroot - this just became way easier :)
Well.... it doesn't dirty the chroot exactly, but you do end up with everything you built being installed so could get unwanted deps further down the rebuild list unless you are careful. I have been meaning to adjust that to put the package in a local repo in the chroot so rebuilt packages could be installed as necessary (much like in the chroot building wiki page) but have not had time.
Added a new section to the wiki - these changes are in git right now, not in the current devtools release: http://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot...