FreeBSD Custom Package Server

[Philip M. Gollucci]

Maxim Khitrov wrote:
> A request for new package should contain in itself all the relevant
> settings. If that means sending the make.conf file from the client to
> the server - fine. Have the build server adapt for each new request,
> build the requested port and dependencies, create the package(s), and
> remove the port from the local system. The client can then download
> the package, build server goes on to process the next request, and no
> disk space is wasted. Am I being a bit overambitious? :)
I think that might drive you batty, as some ports require kernel source,
other build differently depending on how the 'world' was built.

Would ports-mgmt/tinderbox work for you ?

1 jail per OS version (5,6,7,8)
1 ports tree
1 make.conf per configuration



-- 
------------------------------------------------------------------------
Philip M. Gollucci (pgollucci at p6m7g8.com)
c:703.336.9354
Consultant / http://p6m7g8.net/Resume/resume.txt
http://riderway.com / http://ridecharge.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB  B89E 1324 9B4F EC88 A0BF

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.