Date: Wed, 25 Sep 2019 15:52:01 -0700 From: George Hartzell <hartzell@alerce.com> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Questions <freebsd-questions@freebsd.org>, freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Problem overriding ports with portshaker. Message-ID: <E5643646-1219-4F99-A8BB-C279D5965F8A@alerce.com> In-Reply-To: <20190926004936.e32f6d7a.freebsd@edvax.de> References: <23943.45748.104392.96450@alice.local> <23945.3567.44900.631073@alice.local> <20190925041645.GA11443@blogreen.org> <23947.37724.943422.207082@alice.local> <20190926004936.e32f6d7a.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, thanks. Very good pointer, and been there. Should have emphasized that I=E2=80=99m new to the poudriere, multiple = trees, portshaker auto-merging world. Ports in general are not a new = thing, but e.g. PORTSDIR doesn=E2=80=99t come up with your ports tree = always lives in /usr/ports=E2=80=A6. ;) Thanks, g. > On Sep 25, 2019, at 3:49 PM, Polytropon <freebsd@edvax.de> wrote: >=20 > On Wed, 25 Sep 2019 09:18:36 -0700, George Hartzell wrote: >> 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. >=20 > You can find a lot of interesting environmental variables (among > other helpful information) in "man 7 ports". :-) >=20 >=20 >=20 > --=20 > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E5643646-1219-4F99-A8BB-C279D5965F8A>