Reorganization of the py-sqlalchemy ports
olivierd at freebsd.org
Wed May 18 20:06:56 UTC 2016
On Wed, 18 May 2016 08:02:59 +0100
Matthew Seaman <matthew at FreeBSD.org> wrote:
> Dear all,
> The state of the SQLAlchemy ports currently in the tree is pretty dire.
> SQLAlchemy is perhaps the premiere ORM written in Python and we really
> should have decent support for it. Plus I know of at least two new as
> yet uncommitted ports waiting on availability of an up-to-date version.
> Can I draw your attention to PRs 191442 and 205852 and Review D908:
> The scope of changes involved includes, amongst other things, a
> reorganization of what sqlalchemy ports are available in the tree.
> Currently we have:
> Port Version Maintainer
> py-sqlalchemy06 0.6.9 nivit at FreeBSD.org
> py-sqlalchemy 0.7.10 nivit at FreeBSD.org
> py-sqlalchemy-devel 0.8.2 nivit at FreeBSD.org
> I'm proposing the following:
> py-sqlalchemy06 0.6.9 nivit at FreeBSD.org (Deprecate 2016-08-20)
> py-sqlalchemy07 0.7.10 nivit at FreeBSD.org (Deprecate 2016-08-20)
> py-sqlalchemy08 0.8.7 nivit at FreeBSD.org
> py-sqlalchemy09 0.9.10 m.tsatsenko at gmail.com
> py-sqlalchemy10 1.0.13 m.tsatsenko at gmail.com
I wonder, why to create as many SQLAlchemy ports as releases (it's just an ORM after all).
The easiest way, imho is focusing on 1.0.x releases, and having only one port databases/py-sqlalchemy.
> I've marked two of the ports for deletion in 3 months time, on the basis
> that a) upstream has declared those ports EoL and b) 5 different
> versions of the same package is really a bit much.
> During that three months, there is further work to do on consumers of
> SQLAlchemy in the tree: most consumers should work happily with more
> recent versions, but currently most of them are depending on version
> 0.7.x as the generic 'py-sqlalchemy' port. This will all need testing,
> Comments, constructive criticism and reviews welcome.
Olivier Duchateau <olivierd at freebsd.org>
More information about the freebsd-ports