Re: End of Python 2.4–2.6 and 3.1–3.3 support

[Ryan Schmidt]

On Oct 11, 2014, at 7:01 AM, René J.V. Bertin wrote:

> On Saturday October 11 2014 06:53:27 Ryan Schmidt wrote:
> 
>> 
>> Obviously, the naming is intentional. p5.12-X ports use perl5.12, p5.16-X ports use perl5.16, etc.
>> I don't understand. If a port depends on p5.12-X, then it will use p5.12-X.
> 
> Obviously, yes. But what if a port depends on functionality provided by p5.y-X which isn't available in p5.12-X because it depends on a newer perl version? I suppose that was at the heart of my problem: at some point updates for p5.12 (replace 12 with any other version) cease...

If a port depends on p5.12-X but p5.16-X would work, the port should update its dependency. 5.16 is the default version of perl in MacPorts at this time which all ports that require perl functionality should use, unless other versions are needed for special reasons.

If a port depends on a port that doesn't provide the required functionality, then obviously the port should update its dependency then too.


>>> an older version if needed. What's missing there is a way to "hold" a port, so that uninstall inactive won't touch it.
>> 
>> We do have "sudo port setrequested ..." and "sudo port unsetrequested ..." which could be used for that.
> 
> After setrequested `uninstall inactive` won't touch it? These seem to be orthogonal, independent properties ...

No, I'm saying MacPorts has the capability for you to record which ports you want and which are just there for other reasons. You can use that to your advantage:

Run "port installed requested" and verify that all ports printed are indeed ones you want.

Run "port installed unrequested" and verify that all ports printed are indeed ones you don't care about.

If needed, use "sudo port setrequested" or "sudo port unsetrequested" to fix the above lists.

Then you can clean up by running "sudo port uninstall inactive and unrequested".