On 27/11/2020 21:24, Connor McLaughlan wrote:
On Fri, Nov 27, 2020 at 1:52 AM Ottavio Caruso
<ottavio2006-usenet2012%yahoo.com@localhost> wrote:
On 26/11/2020 15:23, Benny Siegert wrote:
On Thu, Nov 26, 2020 at 4:19 PM Mayuresh <mayuresh%acm.org@localhost> wrote:
Sorry, I missed the point. I should not do bootstrap? I thought that's
necessary to get pkgsrc set.
Only on non-NetBSD systems. Think of the NetBSD base as having a
default bootstrap included.
What of you do a second bootstrap on NetBSD? Let's say pkgsrc-current on
top of the stable packages?
--
Ottavio Caruso
If you use a second live pkgsrc on the same system it can only reside
in a location apart from /usr/pkgsrc, /usr/pkg ...
You have to keep all intersections apart and cannot use prebuilt
binary packages from a /usr/pkgsrc build on a /usr/pkgsrc-current,
/usr/pkg-current setup.
So you also have to clear your path variable of reference to /usr/pkg
and replace them with your new second pkgsrc and also bootstrap that
pkgsrc because the build tools and everything will need to be adjusted
to the new paths and will result in building a bmake that knows how to
handle them. So you need to compile and run stuff on the new pkgsrc by
setting up your path and using the correct bmake instead of the system
make.
Still, you're sharing $VARBASE, which, unless set otherwise, defaults to
/var.
--
Ottavio Caruso