The Python SQL Toolkit and Object Relational Mapper
SQLAlchemy is the Python SQL toolkit and Object Relational Mapper that
gives application developers the full power and flexibility of SQL.
It provides a full suite of well known enterprise-level persistence
patterns, designed for efficient and high-performing database access,
adapted into a simple and Pythonic domain language.
WWW: http://www.sqlalchemy.org/
===> The following configuration options are available for py27-sqlalchemy08-0.8.2_1:
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
TESTS=off: Include nose for unit tests
====> Options available for the multi BACKEND: you have to choose at least one of them
MSSQL=off: Microsoft SQL Server support
MYSQL=off: MySQL database support
PGSQL=off: PostgreSQL database support
SQLITE=on: SQLite database support
SYBASE=off: Sybase backend
===> Use 'make config' to modify these settings
Reorganise and modernise the py-sqlalchemy ports.
- Introduce new ports for the sqlalchemy 0.9 and 1.0 release branches.
- Deprecate the ports for the 0.6 and 0.7 release branches, as these
have been declared EoL and are no longer supported by upstream.
- Update to the latest available version in each branch.
In detail:
Port Version Maintainer
----------------------------------------------
py-sqlalchemy06 0.6.9 nivit@FreeBSD.org (Deprecate 2016-08-20) [1]
py-sqlalchemy07 0.7.10 nivit@FreeBSD.org (renamed py-sqlalchemy,
Deprecate 2016-08-20) [1]
py-sqlalchemy08 0.8.7 nivit@FreeBSD.org (renamed py-sqlalchemy-devel)
[1]
py-sqlalchemy09 0.9.10 m.tsatsenko@gmail.com (new, repocopy from
py-sqlalchemy-devel) [2]
(Only the first 15 lines of the commit message are shown above )
Remove UNIQUENAME and LATEST_LINK.
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336
Switch PYTHON_REL from a 3 digits number to a 4 digits number to handle
python 2.7.10
Differential Revision: https://reviews.freebsd.org/D2639
Reviewed by: sunpoet, mva
databases/py-sqlalchemy-devel: support staging and do general clean-up
- do not use easy_install for installation and convert to auto-generated packing
list
- remove options descriptions, that already presented in bsd.options.desc.mk
- utilize options helpers
- install docs and examples into staging area uncoditionally
- remove inclusion of devel/py-virtualenv/files/py3k-fix-pkg-plist.inc - it's
implemented in bsd.python.mk
- bump PORTREVISION because of package change
Approved by: nivit (maintainer, explicitly for such changes in his ports)
- Update to 0.8.2
- Remove leading indefinite article from COMMENT
- Run 2to3 command on lib, doc and examples dirs,
when Python ver. >= 3.0
- Remove files/patch-setup.py (pass --always-unzip
to PYDISTUTILS_INSTALLARGS instead)
- Switch off MYSQL and PGSQL options (wanted by
koobs@, via private email)
- Add devel/py-mock to TEST_DEPENDS, when Python
ver. < 3.3
- Fix path to py3k-fix-pkg-plist.inc
Build log: http://goo.gl/kF8pT
Release notes: http://goo.gl/CKfHc
- Repocopy databases/py-sqlalchemy to databases/py-sqlalchemy-devel
- Update the repocopied port to 0.8.1 [1]
- Re-order OPTIONS conditionals [1]
- Make BUILD_DEPENDS use TEST_DEPENDS when TESTS option is true [1]
PR: ports/178498 [1]
Submitted by: koobs
