On Tue, Dec 04, 2018 at 01:28:29PM +0000, Edward Lopez-Acosta wrote: > Daniel, > > Not sure how much you looked into this besides the 30 sec noted, but nothing > requires py-pygfm in the ports tree for py2 or py3. The python markdown > module has had a lot of improvements since 2015 (current version in the ports > tree) including cleaning up of dead code, improved testing, and improved > docs. All of which are important to the OpenBSD project per the FAQ. > If gfm doesn't want to keep up with this then I propose it gets dropped since > it then conflicts with the OpenBSD project notes above and it isn't required > by anything. > > Looking at py-cheetah as well, which as noted is 8 years old in the tree, > most of it's dependant projects are dead from what I can tell. Should this > also be kept? I didn't bother to chase down deps of deps because that seems > like a waste of time given this information. >
Edward, we can't just drop random ports to be able to update one other port. we have users, and we don't maintain ports tree just for pleasure. ports which are here could have users, and if the port still have an active maintainer, it should be discussed with him too. As I understand the thread, it is good you already did it for updating textproc/py-markdown. Now if we can't update textproc/py-markdown because of textproc/py-pygfm, it is another thing. this other port has a maintainer too, so he should be contacted too. It would be depleasant for everybody if we update textproc/py-markdown without take care of textproc/py-pygfm. At minimal it will be just disrespectful for textproc/py-pygfm maintainer. Please note I don't say we shouldn't remove obsolete ports. Removing textproc/py-pygfm could be a good thing, but who know ? look at ports@ archive how ports are removed. it is discussed, as for any changes in the tree, and the maintainer is in the loop. Usually removal is done because there is no users, or alternative is possible (and not too problematic to move to), ... it isn't just "it is in the way to update another port", specially if the motiviation of updating this port is just "it isn't the latest release". If you want ask to remove a port, it is possible. but you should start a specific thread for this port removal, Cc the maintainer, motive the removal (updating a port could be a reason). And it is more work for a commiter to remove a port (the removal is registered to help users that just do `pkg_add -u') than to update a port. And once nothing will break if we update textproc/py-markdown, it will be updated. All this work has to be done. if you propose an update for a port, we suppose you already check all of that in some way. if it isn't the case, you should understand it isn't the same amount of work for the person that will look at your diff. so don't expect too much if you did only half of this work. Thanks. -- Sebastien Marie
