Re: Problem overriding ports with portshaker.
Yes, thanks. Very good pointer, and been there. Should have emphasized that I’m new to the poudriere, multiple trees, portshaker auto-merging world. Ports in general are not a new thing, but e.g. PORTSDIR doesn’t come up with your ports tree always lives in /usr/ports…. ;) Thanks, g. > On Sep 25, 2019, at 3:49 PM, Polytropon wrote: > > 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. > > You can find a lot of interesting environmental variables (among > other helpful information) in "man 7 ports". :-) > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problem overriding ports with portshaker.
[resending to ports@ with correct sender address] On Wed, Sep 25, 2019 at 09:18:36AM -0700, George Hartzell wrote: > Setting PORTSDIR fixes it for me (different directory, but it works). Excellent! I released portshaker 1.0.18 which address your issue and updated the port accordingly. Thank you for reporting it. Regards, Romain -- Romain Tartière http://romain.blogreen.org/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) signature.asc Description: PGP signature
Re: Problem overriding ports with portshaker.
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. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
