Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Sep 2019 19:19:16 +0200
From:      Romain =?iso-8859-1?Q?Tarti=E8re?= <romain@blogreen.org>
To:        George Hartzell <hartzell@alerce.com>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>, freebsd-ports <freebsd-ports@freebsd.org>
Subject:   Re: Problem overriding ports with portshaker.
Message-ID:  <20190925171916.GA37113@blogreen.org>
In-Reply-To: <23947.37724.943422.207082@alice.local>
References:  <23943.45748.104392.96450@alice.local> <23945.3567.44900.631073@alice.local> <20190925041645.GA11443@blogreen.org> <23947.37724.943422.207082@alice.local>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
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 <romain@blogreen.org>        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)

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----

iQGzBAABCAAdFiEEgjSaeOfAuAcLWYD/uk0dlVESM28FAl2LoZQACgkQuk0dlVES
M29tngv+Jgjo3pqcn82MVlMj5n47NPK6/tvRvA0MypFqIxFLWMeNrQ41yjcdYBZy
HBVek9LJMxguFvUm5/cFLBb1EORLt88/I96ZQZQ8KWMqM8Yc7kLcoUdoh0VsDEpq
5uunZgMECBPvuCI8Q2Lq01P9Jt2DbnBIur4FWxdmh8WVPq4Yw6zyBMSeD8SBFrKC
mY5BGu2pA12r/7mVgqqeIxgbc25GqWlXBol5mJfHUmevZnIyB9+vhhw5PUUlb1MA
/2a3+5kg2c/hnTKhdSFrQPWtzs/Hz5VJN1dvD+Fg5FRTur8DLS3ffYATIZtMjR7I
kiw6kQ6LgIoh6vI9kPNUQv9uXJwsWy3CRsPJWe7jRljCoBEUXWDDfCQZmheXde7U
cOg+gZEe47yveEqp0Hs8pE9clacH8+qq2zMZZE5k3+8WmYZemghwtN+4VExPW4yO
ayqSEF3RV3EVHgj0PusOtcOLdDEnC8poLAmY9wSjbWkoRX0wM9rbdVzyT9TyEVV2
C+4NaYnp
=0tar
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190925171916.GA37113>