On 9/7/20 3:43 AM, Stuart Henderson wrote: > On 2020/09/06 20:45, Aisha Tammy wrote: >> Hi, >> I've noticed that the sphinx in ports is *really* >> old and hasn't been updated for quite sometime. > > For a long time it had an inactive maintainer listed, which is quite > offputting when updating a port, especially one that is more than just a > quick version bump. > >> I understand that its got a huge amount of reverse dependencies >> and can't just be updated at will, but I was wondering if it might >> be possible to add something like py-sphinx3 which is a different >> package and then is possible start shifting packages? >> >> I am trying to see if I should do this if there's any interest or if >> people would prefer to do it some different way? >> Quite some packages would be upgradable if sphinx is updated. >> >> Best, >> Aisha >> > > It's only ~50 ports. To my inexperienced self, *only* 50 is a lot :P
> pypy is a bit slow to build, the others are fast > enough. Better to do a standard update if possible, experience shows > that having multiple versions of a popular port is a bit of a pain to > deal with. > > If it turns out there are things which *import* sphinx that need a > python2 version we may need a temporary py2-sphinx port held back at an > older version. But if they only use the command-line tools (sphinx-build > etc) then that's not necessary. > I'm first slowly going and updating the dependencies of sphinx and then checking up on the reverse deps. Currently I'm just doing the update, not keeping any temp version. Will see what breaks. Aisha
