Hallo Dan Casey,
I am setting up a single server as a 'build box' for our freebsd
servers. We want to build our own packages because
1. we may need to compile certain ports with different flags then
freebsd chooses.
You can cutomize the build with /etc/make.conf,
or createing a
On 2007-Apr-03 11:42:20 -0400, Dan Casey [EMAIL PROTECTED] wrote:
What I'm setting up is a regular ports tree (/usr/ports) which is Not
updated. Then a second tree /usr/local/current-ports which is updated
daily with portsnap.
I suggest that you mirror the CVS repository (via CTM or CVSup) and
Peter Jeremy wrote:
On 2007-Apr-03 11:42:20 -0400, Dan Casey [EMAIL PROTECTED] wrote:
I'm not sure what to do about the INDEX files, which is
what i had trouble finding documentation on.
Your only option here is cd /usr/ports make index - which is quite
slow (try it and see). You
Thanks all,
I think i'm going to have to check out tinderbox. It's going to be
less of a pain to have an ongoing QA process then it is to maintain this
the way I want to. I would be happy using the freebsd provided
packages, but they are either not compiled the way I would like them.
If
Dan Casey píše v út 03. 04. 2007 v 11:42 -0400:
I am setting up a single server as a 'build box' for our freebsd
servers. We want to build our own packages because
1. we may need to compile certain ports with different flags then
freebsd chooses.
2. We want to update ports only when needed.
On Tue, 03 Apr 2007 11:42:20 -0400
Dan Casey [EMAIL PROTECTED] wrote:
I am having trouble finding documentation that goes in more detail
then that of the handbook. I am sending this message in hopes that
you may be able to point me in the right direction, or know of a
better way to
Dan Casey wrote:
...
What I'm setting up is a regular ports tree (/usr/ports) which is Not
updated. Then a second tree /usr/local/current-ports which is updated
daily with portsnap.
Packages make this kind of messing unnecessary. Having an up to date ports tree
doesn't force you to update
