Date: Wed, 18 May 2016 08:02:59 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Reorganization of the py-sqlalchemy ports Message-ID: <03d3359e-0c33-76e2-5059-8d9caaab832e@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3Ui6qrpXRmaBBijXeANAeiQV13VWGHl3q Content-Type: multipart/mixed; boundary="librJMvahTnC4oHu28MNCR7SSlAWTi3I3" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Message-ID: <03d3359e-0c33-76e2-5059-8d9caaab832e@FreeBSD.org> Subject: Reorganization of the py-sqlalchemy ports --librJMvahTnC4oHu28MNCR7SSlAWTi3I3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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=3D191442 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205852 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'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 --librJMvahTnC4oHu28MNCR7SSlAWTi3I3-- --3Ui6qrpXRmaBBijXeANAeiQV13VWGHl3q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXPBOjXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATKTwQAIlmP3U3LyLk/XrEAILEy4p0 j/VwDYqPV0HMVj1kVfFYgqGPFFOo1s7x5346BcuN7YgFjkA4A8zL3y0fg88fPluV VUmWUE806XiGF+OtMqrWnA3PlPih6Y1zDLnc934GTzqVnMsj745FJCDhvV7gyZbM bq9fu6yVMRWP2DQ5C/E7PLiy7b5k2DfduSiN9NmDAYD9Zg9hn3j3nFC4rcMCojBD b/ojj5WRe334ll/jRHkyEamjAD5KjwmTQJOEwFJ1Ct0hvXQe++u1fjMU2cWm6fLE AejtnYWZ9KWWdArjUk2tAL8y5MQK3Sdli8Rd8l8lSoc91oDjdqTv2emYqxmhO3KA XHaENOeJJE03/6ws5Blan4qcYqIn694ruIhUo19dfvXUAd2EXSOMhx2LQZX0uwAU FKhzLNv84kCjSP3i/zKaddifVgNGvE3H80rmvMcOCl/EuTGq+xIzi3aIo7CEi8Ak j9vLT9FZ1y9qmtExD1X84pHVCc39k0RNIPJumOUySArOdhVVq4ga/icbih94eeTs sFJc/imjLMZnO/pzAjpnHLMAU/qzOmPCfgucDekjkIeOHIPeBNa+OUGjOZSd6sLq ZFksqglNbEx18cu70fb8f0AeWYP2sLPEUyW3Nm8GxzJ5uChOWdQFP61J5QUL3/6p PMDfC122AZU5MdB2ZkSb =TFtI -----END PGP SIGNATURE----- --3Ui6qrpXRmaBBijXeANAeiQV13VWGHl3q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03d3359e-0c33-76e2-5059-8d9caaab832e>