Issues with the port dependency table
Joe Marcus Clarke
marcus at marcuscom.com
Fri Aug 1 00:50:16 EDT 2008
On Thu, 2008-07-31 at 12:14 -0700, Ade Lovett wrote:
> On Jul 31, 2008, at 11:46 , Joe Marcus Clarke wrote:
> > I agree, and this is why I didn't do this earlier. That said, this
> > table isn't authoritative, as it will only used by external tools
> > (i.e. TB still relies on the Makefile generated at build time). As
> > for rescan, addPort IS a rescan. It can be run on a port already in
> > the datastore, and all of that port's properties will be updated
> > (including the dependencies).
> Perhaps we should, for the sake of completeness, add:
> tc rescanPorts -b <buildname> | -a
> which would pull a list of ports on a per-build (or everything) basis,
> and call addPort, to keep the table up to date?
> As you said, since the table is not (yet?) used by tinderbox itself,
> it's not so much of an issue, but I think we should consider at least
> providing the mechanism to more easily keep it up to date.
> Thoughts? Should be trivial enough to code up, and we may find
> ourselves actually using the table in future.
I added the command. I pushed the port listing into the Perl code so we
only need to build the MakeCache once.
> tinderbox-list at marcuscom.com mailing list
> To unsubscribe, send any mail to "tinderbox-list-unsubscribe at marcuscom.com"
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: This is a digitally signed message part
More information about the tinderbox-list