Using Tinderbox as a package builder

[Ion-Mihai Tetcu]

On Mon, 17 Oct 2011 14:36:31 -0700
Jason Helfman <jhelfman at e-e.com> wrote:

> On Tue, Oct 18, 2011 at 01:24:34AM +0400, Dmitry Morozovsky thus
> spake:
> >On Mon, 17 Oct 2011, Tim Bishop wrote:
> >
> >> Hi all,
> >>
> >> I've been using Tinderbox for testing ports for quite a long time.
> >> It does a great job, thanks!
> >>
> >> Now I'm looking at providing binary packages for a bunch of servers
> >> and it seems like a good idea to use Tinderbox to do this as well.
> >> At a simplistic level I could just do this on a regular basis:
> >>
> >> 1. Update ports tree
> >> 2. Queue my list of leaf ports for rebuilding
> >>
> >> Whilst this would do what I need, it would rather pointlessly
> >> rebuild all of the leaf ports regardless of whether they needed
> >> rebuilding. What I need is a way to only rebuild those that have
> >> changed.
> >>
> >> I'd also like to use custom OPTIONS for building some of the ports.
> >> This is easy enough to do with Tinderbox, but I'd need to generate
> >> an INDEX file using the same options to get the dependencies right.
> >>
> >> I've got enough experience of using Tinderbox and ports to script
> >> this myself, but I thought I'd send a mail here first to see if
> >> anybody else has already done the same.
> >
> >Isn't -norebuild option your best friend? ;)
> What does this option really do? I see this from the README, but it
> really doesn't explain things that much.
> 
> -norebuild 	do not force a rebuild of packages specified on
> the command line

Don't rebuilt it if the port didn't change; Marcus has been kind to add
it when I needed it for QAT.


--