[Bug 205852] Be nicer about multiple sqlalchemy ports

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Feb 2 17:31:18 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205852

--- Comment #15 from Palle Girgensohn <girgen at FreeBSD.org> ---
(In reply to Mikhail Teterin from comment #14)

OK. I would prefer we just had one sqlalchemy port, and bend the other ports 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: 

make quicksearch key=sqlalchemy |grep ^Path | cut -f7- -d/                
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...

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-ports-bugs mailing list