Using an older port to make another port

Jeremy Huddleston Sequoia jeremyhu at
Sun Mar 5 00:44:41 UTC 2017

You could just locally revert the offensive change to libarchive until your issue is addressed.


> On Mar 4, 2017, at 13:18, Michael <keybounce at> wrote:
> How do I use an older port when making another one?
> I followed the instructions for working with an older version of libarchive.
> Going back to 97887a375da5d0f6abee018b145833aa02e2bda7 gave me libarchive @3.2.2_1 as a pre-built binary, no problems.
> Now I'm trying to build cmake, which wants libarchive. I've got my git clone at the same (unchanged) checkout, but attempting to install it wants to rebuild libarchive.
> In other words, the version of libarchive currently installed matches the version at 97887, but building cmake at 97887 ("sudo port install", from the devel/cmake directory) wants to build a fresh libarchive (apparently using the system install port tree).
> How do I make this work?
> And how do I then fix anything else that expects a cmake? (as it will probably try to use the system definition of cmake, which will use the system definition of libarchive, which will break).
> ---
> Entertaining minecraft videos

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4465 bytes
Desc: not available
URL: <>

More information about the macports-users mailing list