I vote for killing a lot of them. Apache 1 for instance is a very bad thing to be running right now. If they are EOL upstream, keeping them around is also a bit of false hope to people that might need them. I know I for one could not fix some of these builds since I don't have old enough OSes, and I don't really care to.
—Mark _______________________ Mark E. Anderson <[email protected]> On Thu, Feb 4, 2016 at 5:47 PM, Jeremy Lavergne <[email protected]> wrote: > On 02/04/2016 03:32 PM, Joshua Root wrote: > >> The question is: what should be the general policy with these ports? > >> How long should we keep them around? > > > > As long as they still build on some OS X version that base works on. If > > they break and nobody steps up to fix them, that's a pretty good > > indication that it's time for them to go. > > > > As you mentioned, there are all kinds of reasons why people have to test > > against old versions. A deprecation warning in the description and notes > > would be a good idea. > > > Could this be considered reinforcing the expectation of no one fixing > tickets? > > If people need to use the very old versions, we should encourage them to > use source control to look up these Portfiles. While stubbing ports with > this message would be helpful, I worry how many ports would become stubs. > > _______________________________________________ > macports-dev mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-dev >
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
