| 1 |
On Sat, 2006-11-04 at 15:45 -0800, Robin H. Johnson wrote: |
| 2 |
> 3. The solution is for each enterprise to have their own tinderbox / |
| 3 |
> build-machine. Tinderboxing is supported under catalyst, and I believe |
| 4 |
> there is at least one other tinderbox implementation around. |
| 5 |
> 4. (Assuming catalyst, as it's the only tinderbox I'm familiar with) The |
| 6 |
> enterprise defines a specfile that describes each of their unique |
| 7 |
> environments, and feeds these to tinderbox. Tinderbox generates sets of |
| 8 |
> binpkgs for each environment, which the enterprise then deploys. |
| 9 |
|
| 10 |
Tinderbox (in catalyst) is designed more for testing. Using the stage4 |
| 11 |
catalyst target will save you a good amount of time, since it doesn't go |
| 12 |
through the unmerge/rsync/emerge cycle on each package. Just FYI. |
| 13 |
|
| 14 |
-- |
| 15 |
Chris Gianelloni |
| 16 |
Release Engineering Strategic Lead |
| 17 |
Alpha/AMD64/x86 Architecture Teams |
| 18 |
Games Developer/Council Member/Foundation Trustee |
| 19 |
Gentoo Foundation |
Archives