Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 02 Jan 2013 21:41:33 -0500
From:      Fbsd8 <fbsd8@a1poweruser.com>
To:        Walter Hurry <walterhurry@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: using /etc/portsnap.conf
Message-ID:  <50E4EFDD.5010801@a1poweruser.com>
In-Reply-To: <kc2mcc$c8g$1@ger.gmane.org>
References:  <50E46E0D.5030202@a1poweruser.com> <kc1u0e$mpk$1@ger.gmane.org> <50E4C628.8050207@a1poweruser.com> <op.wqa55untg7njmm@michael-think> <50E4D9A7.8070604@a1poweruser.com> <kc2mcc$c8g$1@ger.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Walter Hurry wrote:
> On Wed, 02 Jan 2013 20:06:47 -0500, Fbsd8 wrote:
> 
>> Thanks that was it.
>> Sometimes your to close to the trees to see the forest.
> 
> But you wouldn't have needed any REFUSE lines if you had followed my 
> suggestion and just extracted the ports you wanted.
> 
> 

After doing portsnap fetch for the first time followed by
"portsnap extract mis/ytree" will create an /usr/ports directory empty 
of the files and directories needed for the "make" command to function. 
But yes the /usr/ports/misc/ytree port will be there.

But having a /etc/portsnap.conf with REFUSE statements for all of the 
ports categories will populate /usr/port directory with only the files 
and directories required for the "make" command to function correctly.

In csup this was called the "base" category which could be selected 
separately in the same way other ports could be selected separately.

But it's good to know that I can duplicate what I was doing with csup 
now with portsnap to have a ports tree trimmed to only the things 
required by "make" and the few major ports that I needed to recompile to 
change the defaults used in the packaged versions. And to address the 
dependents question. I used pkg_add -r to install the dependents and the 
"make install" compiled without any problems.

So thanks for your pointer to "portsnap extract mis/ytree". It took some 
testing to figure out things because the man portsnap is not very clear 
about what is really happening.





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