Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 May 2016 22:04:34 +0000
From:      Olivier Duchateau <olivierd@freebsd.org>
To:        Matthew Seaman <matthew@FreeBSD.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Reorganization of the py-sqlalchemy ports
Message-ID:  <20160518220434.2652aa635577c95c30767045@freebsd.org>
In-Reply-To: <03d3359e-0c33-76e2-5059-8d9caaab832e@FreeBSD.org>
References:  <03d3359e-0c33-76e2-5059-8d9caaab832e@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 May 2016 08:02:59 +0100
Matthew Seaman <matthew@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:
> 
>    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191442
>    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205852
>    https://reviews.freebsd.org/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@FreeBSD.org
>    py-sqlalchemy        0.7.10  nivit@FreeBSD.org
>    py-sqlalchemy-devel  0.8.2   nivit@FreeBSD.org
> 
> I'm proposing the following:
> 
>    py-sqlalchemy06      0.6.9   nivit@FreeBSD.org (Deprecate 2016-08-20)
>    py-sqlalchemy07      0.7.10  nivit@FreeBSD.org (Deprecate 2016-08-20)
>    py-sqlalchemy08      0.8.7   nivit@FreeBSD.org
>    py-sqlalchemy09      0.9.10  m.tsatsenko@gmail.com
>    py-sqlalchemy10      1.0.13  m.tsatsenko@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,
> obviously.
> 
> Comments, constructive criticism and reviews welcome.
> 
> 	Cheers,
> 
> 	Matthew
> 
> 
> 


-- 
Olivier Duchateau <olivierd@freebsd.org>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160518220434.2652aa635577c95c30767045>