Ok, there's got to be a trick for this!

[Joe Marcus Clarke]

On 11/12/11 11:06 AM, John Marino wrote:
> Hi,
> Tinderbox is really smart about knowing when it's port tree is update
> and upgrading the affected packages.  I found out the hard way that
> deleting the package from $BUILD/All is considered the same as updating
> the port.  I assume rebuilding a port manually would be the same thing
> effective.
>
> The problem is that I deleted a root package.  Pkgsrc has a concept of
> "bootstrapDepends" and the digest package is a dependency of every
> single port in the tree.  I deleted this package to force a rebuild, but
> now every existing package thinks it needs to be rebuilt.
>
> I tried touching the package archive with an older date.
> I tried changing the date in the database to match this file date.
>
> Nothing is working, tinderbox is too smart for me.
>
> How can I trick tinderbox into thinking none of the packages need
> rebuilding permanent?  I guess each library that got rebuilt since the
> bootstrap cascades to its own set of rebuilds...  Oh, and where is the
> logic that determine what dependencies need rebuilding?

Tinderbox goes off of version.  So, if the package exists with the 
correct version, it will not be rebuilt.  If you want to avoid 
rebuilding the package specified on the command line, add the -norebuild 
flag to tinderbuild.

Joe

>
> Sure, I could spend 8 hours rebuilding everything, but this has happened
> to me a couple of times and I'd like to have a trick in my hip pocket
> during this testing phase of tinderbox-dragonfly.
>
> Thanks,
> John
>
>
> _______________________________________________
> tinderbox-list at marcuscom.com mailing list
> http://marcuscom.com/mailman/listinfo/tinderbox-list
> To unsubscribe, send any mail to "tinderbox-list-unsubscribe at marcuscom.com"
>


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