Using Tinderbox as a package builder
Joe Marcus Clarke
marcus at marcuscom.com
Tue Oct 25 11:32:40 EDT 2011
On 10/25/11 7:55 AM, Tim Bishop wrote:
> On Thu, Oct 20, 2011 at 12:09:43PM +0100, Tim Bishop wrote:
>> On Wed, Oct 19, 2011 at 09:45:21AM -0400, Steve Wills wrote:
>>>> 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'm curious, what are you running on the hosts to update the packages? I'm
>>> guessing whatever that is needs the INDEX? I'm thinking I could use
>>> something like that as well.
>> [snip my previous details on doing this]
> I've now documented what I did above on my blog. Here's a link so
> anybody else interested can see what I did:
Cool. Chris, what about adding a contrib section to the docs to capture
these kind of external items?
PGP Key : http://www.marcuscom.com/pgp.asc
More information about the tinderbox-list