Mel wrote:
On Monday 26 January 2009 16:39:35 Doug Poland wrote:
On Mon, Jan 26, 2009 at 09:21:55AM -0900, Mel wrote:
On Monday 26 January 2009 08:23:13 Doug Poland wrote:
On Mon, Jan 26, 2009 at 08:25:37AM -0600, Doug Poland wrote:
per...@pluto.rain.com wrote:
I've got a network running different versions of FreeBSD (6.3,
7.0) on different architectures (i386, SPARC64).
What I'd like to do is export the ports hierarchy to all
machines, but preserving ports/packages for each
version/architecture. I also want to make rebuilding indexes
run as fast as possible.
Right now, I simply exports(5) /usr/ports via NFSv3 ...
...
The following 2 lines on each machine in /etc/make.conf should
fix those problems:
PACKAGES=${PORTSDIR}/packages/${ARCH}
INDEXFILE=INDEX-${ARCH}-${OSVERSION:C/([0-9]).*/\1/}
It would seem the package building tools (make package, portinstall
-p) do not honor the PACKAGES setting in /etc/make.conf. The
package is simply deposited in /usr/ports/{category}/{pkgname}. Is
there a way to force the package builder to use this knob?
make package respects it.
Curious... I tested it on two different machines, and make package did
not put the package in the expected location. Perhaps I'm missing
something?
Ah, my bad:
Mk/bsd.port.mk:
do-package: ${TMPPLIST}
@if [ -d ${PACKAGES} ]; then \
$PACKAGES has to be created before it respected.
>
Ah ha! Thanks for that info, and the reference to Mk/bsd.port.mk
--
Regards,
Doug
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
