- devel/py-subversion: cleanup for 1.14 which is LTS too now
- devel/subversion-lts: remove
- devel/subversion: clean up after -lts removal
Details
- Reviewers
lev
Diff Detail
- Repository
- rP FreeBSD ports repository
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 40125 Build 37014: arc lint + arc unit
Event Timeline
- MOVED: fix destination
Updating D30914: Remove devel/subversion-lts which depends on EOL Python 2.7.
Upstream has marked Subversion 1.14.x as LTS next to 1.10.x
- MOVED: fix destination
- update consumers
Updating D30914: Remove devel/subversion-lts which depends on EOL Python 2.7.
Upstream has marked Subversion 1.14.x as LTS next to 1.10.x
- devel/git: merge two RUN_DEPENDS lines
Updating D30914: Remove devel/subversion-lts which depends on EOL Python 2.7.
Upstream has marked Subversion 1.14.x as LTS next to 1.10.x
I was asked by several people to left subversion-lts as 1.10.x till version AFTER 1.14 will be released (and then updated -lts to 1.14).
I'm not sure, maybe we need to bump -lts to 1.14 now instead of removing it and adding it later. There are some organizations which want to use -lts version, and removal is bad for them.
Not sure I follow your first remark, 1.14 is released and marked as LTS: https://subversion.apache.org/download.cgi
So both 1.14 and 1.10 are LTS now. We could also bump devel/subversion-lts to 1.14 but then devel/subversion would be the same port.
Yes, both 1.10 and 1.14 are LTS. When 1.14 had been released, I been asked to leave -lts as 1.10 for some time by -lts consumers. Maybe, now it is not relevant anymore.
Problem is, devel/subversion and devel/subversion-lts are different ports, even if we bump -lts to 1.14.x: yes, version will be the same, but origins will be different and in the future, when (if?) 1.15 will be released, we will need -lts (as 1.14.x) AGAIN. And users of -lts port will need to migrate between ports twice.
I don't think it is good idea, as LTS means "long term support" and its removal and then resurrection looks strange: is it really long term support if you remove it?!
Better to have two ports with same version (for now!), but with different QoS, IMHO.
BTW, why do you want to remove this port? It doesn't depend on python2.7. It install some scripts, which are python27-esque, but it is optional tools. Core "subversion" binary is build & runs without pyhton2.7, I've checked it :-)
devel/py-subversion requires python2 when it is build for LTS, and it could be removed (don't support py-subversion-lts at all).
I think the USES=python:2.7,env marked it as deprecated even though only some auxiliary things like devel/py-subversion need Python 2.7 when build for LTS 1.10.x So we could also push down the deprecation?
sync with main, no further changes
Updating D30914: Remove devel/subversion-lts which depends on EOL Python 2.7.
Upstream has marked Subversion 1.14.x as LTS next to 1.10.x