Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 5 Dec 2002 16:27:57 -0600 (CST)
From:      "Scott A. Moberly" <smoberly@karamazov.org>
To:        <hartzell@kestrel.alerce.com>
Cc:        <freebsd-ports@FreeBSD.ORG>
Subject:   Re: NFS mounting the ports tree.
Message-ID:  <45077.65.221.169.187.1039127277.squirrel@mail.karamazov.org>
In-Reply-To: <15855.52973.469760.370106@rosebud.alerce.com>
References:  <15855.50834.811514.388015@rosebud.alerce.com> <38311.65.221.169.187.1039125234.squirrel@mail.karamazov.org> <15855.52973.469760.370106@rosebud.alerce.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> Scott A. Moberly writes:
>  > [...]
>  > > George originally wrote:
>  > >
>  > >   1) I found the section of the freebsd handbook that explains how
> to
>  > >      set up the distfiles directory and the workdirectory.  This
> still seems to require that the client actually build the
> thing,
>  > > which is what I'm trying to avoid.
>  > >      (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html)
>  >
>  > You can do it, but...  /etc/make.conf would have to be generic, use
> includes based on hostname(1) or manually (script) move
>  > /etc/make.`hostname` around...
>
> I'm happy having make.conf be generic, I don't *think* that's the
> cause of my difficulties.
>
>  > >   2) I've tried just mounting /usr/ports, cd'ing into the directory
> of
>  > >      interest, and doing a "make install".  This fails quickly,
> since
>  > > the INSTALLCOOKIE is there.
>  > >
>  > >      Doing a "make deinstall" then a "make install" works for
> simple
>  > > ports, but sometimes causes recompilation.
>  >
>  > make clean is a quicker alternative
>
> Doesn't a make clean remove all of the stuff that's built?  How is that
> quicker than installing what the big beefy machine has already compiled?

I see what you are doing is a make install onto the 'beefy' machine then a
make install onto the the slower ones.
then just:

rm -f work/.install_done*

should work fastest.

>  > [...]
>  > have /var/db/pkg a temporary mount for building installing.
>
> Again, I'm confused.  I'm hoping to avoid all of the recompiles?

on fast machine:

mount_nfs slow_machine:/var/db/pkg /var/db/pkg
cd /usr/ports/type/package
make clean && make
umount /var/db/pkg

on slow machine:

mount_nfs fast_machine:/usr/ports /usr/ports
cd /usr/ports/type/package
make install
umount /usr/ports


>  > [...]
>  > I personally just mount and let the client build after I have tested
> and reviewed said port.
>
> In my case, my laptop would spend the weekend rebuilding gnome,
> evolution, X, perl, etc....  Yikes.

Understood...  hope the above helps...  on the one intolerably slow
machine I had, the above procedure worked and as the machine died; I no
longer have the scripts around.  Of course, when it comes to dependencies
things need to be scripted.  The above commands become very tedious when
re-building an entire system bottom-up.  I think I used perl and ssh, but
again the script is lost, so I can't just hand you a solution :(  my
apologies.

--
Scott A. Moberly
smoberly@karamazov.org



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45077.65.221.169.187.1039127277.squirrel>