Re: Problem overriding ports with portshaker.

2019-09-25 Thread George Hartzell
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

Re: Problem overriding ports with portshaker.

2019-09-25 Thread Romain Tartière
[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

Re: Problem overriding ports with portshaker.

2019-09-25 Thread George Hartzell
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 S