Using Tinderbox as a package builder
Dmitry Morozovsky
marck at rinet.ru
Mon Oct 17 17:24:34 EDT 2011
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? ;)
--
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: marck at FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
------------------------------------------------------------------------
More information about the tinderbox-list
mailing list