Date: Wed, 25 Sep 2019 09:18:36 -0700 From: George Hartzell <hartzell@alerce.com> To: Romain =?iso-8859-1?Q?Tarti=E8re?= <romain@freebsd.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org>, freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Problem overriding ports with portshaker. Message-ID: <23947.37724.943422.207082@alice.local> In-Reply-To: <20190925041645.GA11443@blogreen.org> References: <23943.45748.104392.96450@alice.local> <23945.3567.44900.631073@alice.local> <20190925041645.GA11443@blogreen.org>
index | next in thread | previous in thread | raw e-mail
Romain Tartière writes: > [...] > Can you try setting PORTSDIR to your target ports tree, e.g. > > % sudo env PORTSDIR=/usr/local/poudriere/ports/default portshaker -M Setting PORTSDIR fixes it for me (different directory, but it works). > My guess is that since Mk/bsd.port.mk was not found, ARCH is not set and > the Makefile is malformed. Sounds right. > If you confirm it fixes your issue, I'll commit something to do this > automagically. It does not really make sense to not set PORTSDIR to the > target ports tree IMO… I wasn't aware of PORTSDIR, I'm a long time ports user but this is my first foray into not simply using the stock FreeBSD ports tree. I assumed (!!!) that portshaker knew everything that it needed to know about where the trees were and was doing all of the magic for me. Thanks for the help! g.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23947.37724.943422.207082>