On 2019/09/26 08:12, Daniel Dickman wrote:
> (Moved from: “Adding binary renaming facility to python.port.mk”)
> 
> > On Sep 25, 2019, at 5:47 AM, Stuart Henderson <s...@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.

For the sake of consistency I was mostly thinking of following the
current py3-only ports and use MODPY_VERSION=${MODPY_DEFAULT_VERSION_3}
without a flavour, it's not too much work to find and update reverse
dep's.

> 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?
> 

My favourite fix would be to get rid of the unflavoured versions and
have FLAVOR=python27 (and change FLAVOR=python3 to FLAVOR=python37 to
allow us to have multiple 3.x versions ..)

This is a fair chunk of work to put in place (a hackathon project,
perhaps), and then we would need to use a different mechanism
for "de-conflicting" installed scripts*, but it would make it easier
to get new major python versions tested before switching the bulk of
the ports tree across, or to cope if we have something important
that is hard to update to work with a newer python version.

Perhaps some might consider this overengineering though :)




* maybe by installing all scripts with a suffix "foo-37", and then a
symlink "foo -> foo-37" only in the "main" version...

Reply via email to