FreeBSD Custom Package Server

[Maxim Khitrov]

On Sat, Apr 5, 2008 at 3:51 PM, Philip M. Gollucci <pgollucci at p6m7g8.com> wrote:
> 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

I'll take a look at it, but from the description it sounds like I'd
have the same problem. For example, I need to install php5 on two of
the machines, but one doesn't need the cgi binary, only cli. There
doesn't seem to be an easy way to separate the two builds without a
second jail.

- Max