2008/1/9, Aaron Griffin <aaronmgriffin@gmail.com>:

On Jan 7, 2008 10:39 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> * Official pacbuild usage
>
> This has gone more and more by the way side. With the advent of a manual machine
> to build packages on for non x86_64 devs, this is less and less of an issue. The
> major push for pacbuild was so that some devs could build on hardware they don't
> run.
>
> Is anyone willing to take up the pacbuild charge here? Give it some new life?

An addendum here. Jason gave us a status report of pacbuild last time.
I lost it in the shuffle when writing up the report, so forgot that it
existed.

The full text is here:
http://archlinux.org/pipermail/arch-dev-public/2007-December/003716.html

So there are a few pending changes, the following will NOT block a release:
   Better logging in Apple and Strawberry
   Automatic chroot rebuilding
   Usage of the chroot tools from devtools
And the following are considered "blocking"
   Ability to 'cancel' a package not currently being built
   Include packages depends/makedepends
   Addition of 'depwait' status for when a dependency has not been
built successfully

Git tree for progress:
http://projects.archlinux.org/git/?p=pacbuild.git;a=shortlog;h=dephandling

So, if we take a look at the last three items that block this release,
we can actually get this up and running without those features.

So, next steps. I'm going to setup my x86_64 build machine as a
pacbuild build machine to start testing things out. Anyone willing to
setup some build machine instances for me? This way we can get it
working and debugging.

See here for more:
http://wiki.archlinux.org/index.php/Pacbuild_Explained#Running_a_build_machine

_______________________________________________
arch-announce mailing list
arch-announce@archlinux.org
http://archlinux.org/mailman/listinfo/arch-announce