On Sun, May 16, 2021 at 08:12:47PM +0100, Stuart Henderson wrote: > On 2021/05/16 14:57, Kurt Mosiejczuk wrote: > > On Sun, May 16, 2021 at 02:50:45PM -0400, Kurt Mosiejczuk wrote: > > > We're now running into python ports that need newer setuptools than the > > > version we have in tree as the last version that supports python2.
> > > This "new" port clones the current version off into devel/py2-setuptools. > > > After committing this and the associated glue (also attached) we can look > > > at updating devel/py-setuptools to a more recent version. > > > Feedback? > > The one port that seems to need tweaking if this goes in is devel/py-test. > > It's the only one that explicitly includes py-setuptools as a RUN_DEPENDS > > but still actually has a python2 FLAVOR. > That's the only explicit one (and I don't understand why it does that; > I think the py-setuptools RUN_DEPENDS in py-test can just be removed > completely + bump), but every py2 port with MODPY_SETUPTOOLS=Yes does > register a run dependency so needs a bump for this change. That's an early one I did, so I may have misunderstood an error message. I'll take a look. > Quite a few; > $ sqlite3 /usr/local/share/sqlports "select count(distinct fullpkgpath) from > Depends where DependsPath = 'devel/py-setuptools'; > 338 Yeah. I need to remember that just because dependencies are added out of sight, doesn't mean they don't count for REVISION purposes. > but portbump can probably cope with most of these, maybe even all > of them. I'll take a look at doing just that. --Kurt
