Ok, there's got to be a trick for this!
itetcu at FreeBSD.org
Mon Nov 14 13:09:12 EST 2011
On Sat, 12 Nov 2011 13:22:32 -0500
Joe Marcus Clarke <marcus at marcuscom.com> wrote:
> 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.
A-0.5 --> B-2.1 --> C-1.0
If the timestamp of C-1.0.tbz is newer that the one of B-2.1.tbz, then
B-2.1.tbz will be outdated in the Makefile so B will be rebuilt, then A.
IMO (testing-wise) is a feature, not a bug.
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
FreeBSD committer -> itetcu at FreeBSD.org, PGP Key ID 057E9F8B493A297B
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 196 bytes
Desc: not available
More information about the tinderbox-list