Adds staging support to www/horde3-meta.
Fix: Patch attached with submission follows:
Over to maintainer (via the GNATS Auto Assign Tool)
horde is active so I'm not resetting this PR, but I will ping it.
horde3 is going to suffer over 20 ports getting removed in two weeks:
Is there a plan to stage these? It's cutting it a bit close...
I am the only one active at horde@ and I do not plan to work on unsupported horde3. There are no more security updates, support for recent PHP versions etc. and I would like to see these ports off the ports tree. As this is a simple PHP application users can install horde3 themselves anyway.
But if there are enough people who insist on having horde3 in the ports tree and are willing to maintain it - I will be happy to give the maintainership away from horde@.
I respect that you want to see this cut, but you're letting it happen by a natural prune process which means people spend energy to try to *avoid* pruning it. If your idea is the remove the ports from the try it would have been helpful to explicitly deprecate it (and more helpful to do it before 31 august since there are over 700 ports going to get cut that day).
I would recommend for the sack of the prunes to explictly deprecate it (if they are all slaves it could done at the master port) so nobody spends more time on it. Or better yet, remove them yourself so the people removing 700 ports have it a bit easier that day.
I have a huge sleep debt right now...
(In reply to Martin Matuska from comment #4)
> But if there are enough people who insist on having horde3 in the ports tree
> and are willing to maintain it - I will be happy to give the maintainership
> away from horde@.
FYI - I don't have evidence of even a single person that insists on horde3, much less willing to maintain it. I'm just looking at expiration and impact logs and horde3 has a big presence on it, that's all.
Thanks, John. So what way do you suggest? Should I set them all on deprecated and move the expiration date to a date earlier than Aug 31?
yes, that's what I had in mind.
Why not pick 20 August? There are several "interactive" ports expiring that day so the pruners (Rene) will already be working on a batch.
I guess the deprecation message should recommend moving to the latest horde.
I want to deprecate the ports but commits with NO_STAGE are not allowed anymore. Should I remove the NO_STAGE lines and mark them BROKEN?
no, just add this line to your commit message:
"Approval by:<tab>portmgr (implicit, not staged)"
That will get you past the svn hook checks.
A commit references this bug:
Date: Wed Aug 13 07:27:33 UTC 2014
New revision: 364758
Horde 3 has been EOLed in April 2012
Deprecate horde3 ports and set expiration date to 2014-08-20
Approved by: portmgr (implicit, not staged)
Thanks Martin, that helps a lot!