[Buildbot-devel] upcoming release plan: freeze 9/5, release 9/12

Darragh Bailey felix at compsoc.nuigalway.ie
Tue Sep 2 11:34:36 UTC 2008

On Tue, Sep 02, 2008 at 01:11:16PM +0200, Didier Trosset wrote:
> A.T.Hofkamp wrote:
> > Didier Trosset wrote:
> > - Create a way to avoid use of hard-coded tar command (ie maybe I want to
> >  use a non-standard tar, different options (gzip or bzip2 
> > decompression?), my tar doesn't know --strip, etc
> Yes. I've already thought using the python tarfile library. I guess I will
> have to, in the end. Does Windows have the tar command, BTW? But this brings
> a lot of manual handling because the tarfile library does not have the
> --strip option. So the extraction must be done by hand, the correct way, I
> mean avoiding the pitfals of directory access rights.
> Does anyone know if the python tarfile library could be enhanced?

You would probably need to add a method that walks the all members of
the tar archive using getmembers() and runs extract(member[,path]) on
each member with a modified path. i.e. modified to strip the number of
path elements that you want to remove.

If you could provide the ability for people to specify a tar command to
use instead of using the internal buildbot class, that would also be useful.

> > It would make more sense to have separate FTP and untar/gzip steps.
> I wondered a long time on this one, yes. But in the end, I decided that I
> wanted this step to be a source step. Using this source step would result in
> having a directory ready-to-be-compiled.

Maybe, but having separate untar/gzip steps make them more usable by
admins in their own configuration.

> > Jean-Paul
> > 
> Didier


"Nothing is foolproof to a sufficiently talented fool."

More information about the devel mailing list