feature request: record build space used
Joe Marcus Clarke
marcus at marcuscom.com
Sun Jul 27 15:42:06 EDT 2008
On Sun, 2008-07-27 at 19:59 +0300, Ion-Mihai Tetcu wrote:
> > But they're not. Everything needed to install a port is copied to the
> > chroot ({pb}/BUILD) during pre-setup. This way, buildscript can
> > install all the dependent packages, build the port, install it, then
> > create the package. So the total space required will be sizeof(jail
> > + dependency tbzs + dependencies installed + port built + port
> > installed + package).
>
> Oh, so the distfiles and and packages are first copied in the chroot? I
> didn't realized that.
>
> > > The way I see it implemented:
> > > - record the space size for the last build if successful.
> > > - record the space size of the last build if unsuccessful and bigger
> > > that the one currently recorded.
> > > - add a ports_fail_pattered to look for 'out of space'
> > > - have the recorded space exported in prePortBuild hook so that one
> > > could use his favorite mount command for /TINDERBOX_ROOT/BUILD_NAME
> >
> > All of this is doable, but we need to come to an understanding of what
> > is counted toward total space. If you agree with what I've said
> > above, then I'll start work today.
>
> [ .. ]
>
> Yes.
>
I have committed this feature. The total size will be tracked in the
database. It can be obtained using tc getPortTotalSize -d DIRECTORY -b
BUILD. It is not displayed in either of the web frontends (unless
someone wants to add code for that).
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://marcuscom.com/pipermail/tinderbox-list/attachments/20080727/1aab4f66/attachment.bin>
More information about the tinderbox-list
mailing list