aboutsummaryrefslogtreecommitdiffstats
path: root/databases/py-Elixir
Commit message (Collapse)AuthorAgeFilesLines
* Convert Python ports to FLAVORS.mat2017-11-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ports using USE_PYTHON=distutils are now flavored. They will automatically get flavors (py27, py34, py35, py36) depending on what versions they support. There is also a USE_PYTHON=flavors for ports that do not use distutils but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if using distutils but flavors are not wanted. A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been added to cope with Python ports that did not have the Python PKGNAMEPREFIX but are flavored. USES=python now also exports a PY_FLAVOR variable that contains the current python flavor. It can be used in dependency lines when the port itself is not python flavored. For example, deskutils/calibre. By default, all the flavors are generated. To only generate flavors for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf. In all the ports with Python dependencies, the *_DEPENDS entries MUST end with the flavor so that the framework knows which to build/use. This is done by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python module with Python flavors, as the content will be the same). For example: RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR} PR: 223071 Reviewed by: portmgr, python Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D12464
* databases/py-Elixir: unexpire by bumping py-sqlalchemy version.rene2016-12-091-5/+2
| | | | | | PR: 213681 Submitted by: vlad-fbsd@acheronmedia.com Approved by: maintainer timeout (nivit, 7 weeks)
* Chase py-sqlalchemy06 expirationantoine2016-11-091-0/+3
|
* Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.mat2016-04-011-1/+1
| | | | | With hat: portmgr Sponsored by: Absolight
* - Convert ports from databases/ and deskutils/ to new USES=pythonmva2014-10-191-3/+2
| | | | Approved by: portmgr (implicit)
* - add LICENSE (MIT)rm2014-02-103-6/+7
| | | | | | | | | - do not use easy_install - convert to using auto-generated packing list - remove tab and add trailing slash in pkg-descr:WWW - bump PORTREVISION Approved by: nivit (maintainer, by email)
* Fix properties on pkg-plistbapt2014-01-221-1/+0
|
* Add NO_STAGE all over the place in preparation for the staging support (cat: ↵bapt2013-09-211-5/+2
| | | | databases)
* - Fix *_DEPENDS after the repocopy of databases/py-sqlalchemynivit2011-06-251-2/+2
| | | | | (This port doesn't yet support SQLAlchemy 0.7.X) - Bump PORTREVISION
* - Get Rid MD5 supportmiwi2011-03-201-1/+0
|
* - Update to 0.7.1nivit2009-12-183-60/+4
|
* - Update to 0.7.0nivit2009-10-273-5/+6
|
* - Update to 0.6.1nivit2008-08-193-5/+60
| | | | | - Add pkg-plist - Add post-install stage to install examples
* - Update to 0.6.0nivit2008-07-262-6/+5
|
* Bump portrevision due to upgrade of devel/gettext.edwin2008-06-061-0/+1
| | | | | | | | | | The affected ports are the ones with gettext as a run-dependency according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT in Makefile (29 of them). PR: ports/124340 Submitted by: edwin@ Approved by: portmgr (pav)
* - Update to 0.5.2nivit2008-04-102-4/+4
|
* - Update to 0.5.1nivit2008-02-172-5/+6
| | | | - Add a secondary download site
* - Set PLIST_FILES to %%PYTHON_SITELIBDIR%%/%%PYEASYINSTALL_EGG%% (as ↵nivit2007-08-241-1/+1
| | | | suggested by sat@)
* - Update to 0.3.0nivit2007-08-063-30/+8
| | | | | - Convert easy_install support to bsd.python.mk's - Remove pkg-plist
* - Make Python 2.5.1 the default Python versionalexbl2007-07-301-0/+1
| | | | | | | | | | - Add significantly better support in bsd.python.mk for working with Python Eggs and the easy_install system Tested by: pointyhat runs Approved by: pav (portmgr) Most work by: perky Thanks to: pav
* A declarative layer on top of SQLAlchemy. It is a fairly thin wrapper, whichnivit2007-02-144-0/+62
provides the ability to define model objects following the Active Record design pattern, and using a DSL syntax similar to that of the Ruby on Rails ActiveRecord system. Elixir does not intend to replace SQLAlchemy's core features, but instead focuses on providing a simpler syntax for defining model objects when you do not need the full expressiveness of SQLAlchemy's manual mapper definitions. Elixir is intended to replace the ActiveMapper SQLAlchemy extension, and the TurboEntity project. WWW: http://elixir.ematia.de
generated by cgit (git 2.34.1) at 2024-12-12 18:15:57 +0800