(Moved from: "Adding binary renaming facility to python.port.mk")
> On Sep 25, 2019, at 5:47 AM, Stuart Henderson <stu@spacehopper.org> wrote:
>
> imo, if there's a good reason to keep the py2 version (used by something
> else in the ports tree, or possibly if it includes a useful compiled
> iextension) then split the port.
>
> but if the py2 version isn't really useful and is holding back an update,
> drop the py2 version.
I'm wondering how you're thinking about this. Something like the below?
Change:
FLAVORS = python3
FLAVOR ?=
To:
FLAVORS = python3
FLAVOR = python3
(Note, I purposely remove the ? above to avoid ability to override FLAVOR.)
I think this approach would minimize changes in reverse dependencies that depend on a FLAVOR.
An alternative approach would be to drop the FLAVORS completely and make what used to be the python3 flavor the new package. But I think that approach might be a bit more complicated because of the reverse dependencies.
Is there an easier migration path?
No comments:
Post a Comment