Date: Tue, 02 Feb 2016 17:31:18 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 205852] Be nicer about multiple sqlalchemy ports Message-ID: <bug-205852-13-gX8MMuW74r@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205852-13@https.bugs.freebsd.org/bugzilla/> References: <bug-205852-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205852 --- Comment #15 from Palle Girgensohn <girgen@FreeBSD.org> --- (In reply to Mikhail Teterin from comment #14) OK. I would prefer we just had one sqlalchemy port, and bend the other port= s to work with the new fresh version only. Just for sport, I got a list of all the ports requiring sqlalchemy and I'm building them all in poudriere:=20 make quicksearch key=3Dsqlalchemy |grep ^Path | cut -f7- -d/=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 biology/pycogent databases/py-Elixir databases/py-alembic databases/py-flask-sqlalchemy databases/py-geoalchemy databases/py-geoalchemy2 databases/py-sqlalchemy databases/py-sqlalchemy-devel databases/py-sqlalchemy-migrate databases/py-sqlalchemy06 deskutils/gourmet deskutils/griffith devel/buildbot games/anki games/childsplay games/pyfa irc/py-limnoria multimedia/py-openlp science/py-obspy www/geeknote www/py-flexget www/py-formalchemy www/py-imdbpy www/py-rhodecode www/py-turbogears2 Then I will try updating the sqlalcemy port and see who fails. As you say, if it the Makefiles that require old versions, perhaps just kick the Makefiles in the right direction is the best option? But I expect to be wrong here, some ports will definitely fail... --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205852-13-gX8MMuW74r>