not trying to rebuild failled ports ?

[Joe Marcus Clarke]

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?

I just updated TB with the new function.  You can get the code from CVS, 
then do:

./tc getPortLastBuiltStatus -d <portdir> -b <build>

And that should tell you if the port built successfully or not.  I'll 
add a feature to not re-build ports on the command line soon.  Hopefully 
those two things will get you where you want to be.

Joe

> 
> 
> Thanks,
> 


-- 
PGP Key : http://www.marcuscom.com/pgp.asc