FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux Development

 
 
LinkBack Thread Tools
 
Old 12-13-2007, 05:35 PM
Jason Chu
 
Default Pacbuild status (was Status Report: 2007-12-11)

> * Official pacbuild usage
>
> This apparently has gone farther by the wayside with the machine I put out there
> for non-x86_64 devs to build packages, taking some of the load off of the guys
> who were waiting for pacbuild.
>
> I'm not even sure of the state here anymore - Simo, Jason, any news? Would you
> guys like root access to the build machine so as to have a place to RUN
> pacbuild? Last I checked I did install it, but it isn't configured or the most
> recent version.

Of the original todo list (posted here
http://archlinux.org/pipermail/arch-dev-public/2007-October/001944.html) I

- started adding better logging to Strawberry and Apple but got stuck. I
have a patch or two if anyone wants to take this up;

- removed multiple architecture support in Apple -- it's just as easy to
run one Apple daemon per architecture;

- started using namcap's new pacman module in update-repos.py;

- gave Apple knowledge of the contents of all its repos;

- added two new statuses (statii?) 'inrepo' and 'depwait'. 'inrepo' is
Apple's knowledge of what packages are in the repos (and what their
dependencies are) and 'depwait' is for a build that is waiting on something
else to be rebuilt.

Still left to do are these sorts of things:

1. better logging in Apple and Strawberry (not blocking)

2. automatic chroot rebuilding (not blocking)

3. using mkarchroot and makechrootpkg (not blocking, though it would be
really really nice)

4. be able to mark 'queued', 'error', or 'done' packages as 'cancelled'
(either through peach or through a command line tool (command line will
probably be easier initially because we don't have any authentication code
in peach))

5. when PKGBUILDs are uploaded with queuepkg, include their depends and
builddepends

6. fitting 'depwait' into the pacbuild flow:

6.1. packages that are 'queued' and depend on packages that are 'queued',
'building', 'error', or 'done' should be set to 'depwait'

6.2. if a package changes status, walk over its required bys and update
their status based on 6.1.

1, 2, 3, and 4 could all be done by other people. I'm probably the best to
do 5, and 6.

1, 2, and 3 aren't absolutely required, but I'd really like to have 3 at
least before we release.

If you want to track my progress check out
http://projects.archlinux.org/git/?p=pacbuild.git;a=shortlog;h=dephandling
. There are actually patches in there. I'm actually doing something!

Jason
_______________________________________________
arch-dev-public mailing list
arch-dev-public@archlinux.org
http://archlinux.org/mailman/listinfo/arch-dev-public
 

Thread Tools




All times are GMT. The time now is 07:26 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org