On Tue, Sep 24, 2019 at 06:26:43PM +0200, clematis wrote:
> On Mon, Sep 23, 2019 at 11:06:39PM +0100, Stuart Henderson wrote:
> > The script conflicts between py- and py3-.
> Hi Stuart,
> Sorry, could you please give me some more details, I am not sure to
> understand this properly.
> I've re-done everything [1] for both FLAVORS, all distinctions in between
> py* and py3* naming were correct on my system using the version attached.
> Including the associated dependencies (py-hamcrest, py-test,
> py-setuptools).
> So I am not sure to understand what you meant by "script conflicts".
> [1] fetch, checksum, extract, patch, configure, build, test, fake,
> port-lib-depends-check, package, install, deinstall
Try installing both flavors at once. You've got a script that is just in
/usr/local/bin without any differentiation. So it will conflict.
The usual method is renaming the python3 version with a "-3" on the
end by using MODPY_SUFFIX
If it was *just* a binary to use and didn't include a library, we might
just make it Python 3.x only to avoid the problem.
You can fix it with a port-install target
post-install
mv ${PREFIX}/bin/base58 ${PREFIX}/bin/base58${MODPY_SUFFIX}
You will need to regenerate the PLIST.
--Kurt
No comments:
Post a Comment