On Thu, Jul 19, 2018 at 01:26:04PM -0300, Elias M. Mariani wrote: > OK, > Nothing personal against the port. > It's just that I think on this port that: > - Is "defunct". > - The only uniqueness is xpra and is now a separate project. So where is your port of xpra ?...
Think about it. You're advocating removing something useful without proposing anything equivalent in exchange. Why should we do the work for you ? > - python 2 only. And my personal concern is that the end of support of > python 2 is coming, of course one can not only remove a port just > because is not python 3 ready... But in this case in the next years > wont be any effort in fixing that. Python 2's death has, unfortunately, been greatly exagerated. I definitely HATE people who will try bringing it about by just saying "hey, python 2 is dying, oh look, there's some other old software for which there is *no equivalent* in the ports tree that's python 2 only. So I must be right". Which is *exactly* what you're doing here. You want to help in killing python 2 ?... figure out how to update ports that are still relevant because they're python 2 only. Hint: updating them is updating them, not saying "hey it's old stuff, let's kill it". > - I don't think that anyone use that port anymore, but no evidence of > that, it would be interesting to see the downloads of each package to > see if is used, not to make decisions based just on that but it would > help in this cases. > > So, I will forget about removing for now, but keep it in mind for a > possible port cleanup. :) Port xpra first. Another good reason to KEEP x11/partiwm: it's TINY. My last bulk shows it taking 41 seconds to build. FORTY ONE SECONDS. Out of a bulk that takes about 24 DAYS when you take all the ports into account. Comparatively, a lot of modern stuff that people have pushed for because, you know, it "replaces old stuff", takes HUGE amounts of time, cpu, memory to build. It's also pushing out old platforms, little by little. Because you know, that recent hyped stuff uses all the cool new tools and languages. And a lot of them do not even build on !amd64. Because you know, anything !amd64 is old and useless...
