The short answer is "by hand".

I look through the dependencies and make sure I install the stuff that is
required before I install the actual package on the little machine.  On the
big machine, I just suck it up.

The Big machine has a huge hard drive, and unless I actually set the package
up to start on the big server, it's just taking up space I wouldn't use for
anything else anyway.

What I should start doing is "make package" and packagize the programs.
That way the package system will handle the dependencies through binary
packages.  Since the whole tree is exported, the binaries go along with the
distfiles and the directories as a free ride.

Dave

> -----Original Message-----
> From: tech-pkg-owner@netbsd.org [mailto:tech-pkg-owner@netbsd.org]On
> Behalf Of Jukka Marin
> Sent: Monday, May 21, 2001 2:43 PM
> To: Dave Burgess
> Cc: Georges Heinesch; tech-pkg@netbsd.org
> Subject: Re: 2 pkgsrc questions
>
>
> On Mon, May 21, 2001 at 02:26:30PM -0500, Dave Burgess wrote:
> > I NFS mount the entire pkgsrc directory (which I put on
> /usr/pkgsrc) from
> > all 25 of my servers.  This has the added benefit of being able
> to build the
> > packages on the 800MHz Pentium 3, and install them on the
> 100Mhz 486.....
>
> How do you do that?  If you do "make" in pkgsrc/a/b and package b depends
> on pkgsrc/c/d, doesn't package d get installed on the 800 MHz
> machine before
> b is built?
>
>   -jm
>