[arch-dev-public] automatic package builder

Aaron Griffin aaronmgriffin at gmail.com
Fri Sep 25 11:37:40 EDT 2009

On Fri, Sep 25, 2009 at 4:01 AM, Xavier <shiningxc at gmail.com> wrote:
> By the way, I am curious about pacbuild :
> http://wiki.archlinux.org/index.php/Pacbuild_Explained
> What do people think about it ?

Honest opinion? It was over-engineered from the start and is far to
complex to use. You need like 3 daemons running, and have to do manual
database insertions (why does it have a database?!) to configure

- - - - -

makechrootpkg was made in such a way that is can and should be used
for this purpose. Here's how I would setup a "build machine".

a) Create two global chroots, one for "current" and one for "testing".
We'll call them /var/archroot and /var/archroot-testing (alternative:
append arch on there and create 4 total. Requires a 64bit machine and
linux32 usage)

b) Scan svn commits SOMEHOW. This could be done by watching the
arch-commits list, or simply running "svn up" in a job and parse

c) For each trunk commit found, do an svn export of the trunk and run
"makechrootpkg -c -u -r/var/archroot -l $pkgname"

d) Update the read-only layer of the chroot periodically with
"mkarchroot -u /var/archroot/root"

e) Run namcap on PKGBUILDs and resultant packages

f) Place built packages in a specific staging ground we have access
to. They still require testing before being promoted to the repos.

As for notifications, we webpage AND email notifications would be
ideal. Perhaps batched emails every hour or so? "The follow packages
work / The following failed hard"?

More information about the arch-dev-public mailing list