not trying to rebuild failled ports ?

[Joe Marcus Clarke]

On Tue, 2008-05-13 at 16:45 +0300, Ion-Mihai Tetcu wrote:
> On Tue, 13 May 2008 09:21:49 -0400
> Joe Marcus Clarke <marcus at marcuscom.com> wrote:
> 
> > On Tue, 2008-05-13 at 10:50 +0300, Ion-Mihai Tetcu wrote:
> > > Hi,
> > > 
> > > 
> > > I'm running an exp build on one of my tindys. I have to build all ports.
> > > 
> > > I'm building them like:
> > > ./tc addPort -b ${_build} -r -d ${PORT} -o
> > > ./tinderbuild -noduds  -nullfs -plistcheck -b ${_build} ${PORT}
> > > 
> > > I'd like two things:
> > > - not to rebuild ports already build OK (I guess I can check this from
> > > my build script be interrogating the database and skip the port if it
> > > was built OK)
> > > - have tindy not trying to rebuild ports that already failed: if the
> > > port was already tried before (either via ./tinderbuild or as a
> > > dependency of an other port) I don't want tindy to loose time trying to
> > > rebuild it since it will fail for sure.
> > > 
> > > Any way to achieve this ?
> > 
> > I assume if there were a getPortLastBuiltStatus function for tc, you
> > would have what you need?
> 
> That would be obviously OK for 1, but how would it help me for 2?
> 
> If A and B depends on X, it tried to build A and failed because of X,
> then I don't want it to try again for either ./tinderbuild X or when
> trying to build B. Am I missing something?

If port X failed, then the status of ports A and B will be DEPEND
indicating a dependency failed.  Port X's status will be FAIL.

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/20080513/6c7bbdae/attachment.bin