aboutsummaryrefslogtreecommitdiff
path: root/devel/bzr-pipeline
Commit message (Collapse)AuthorAgeFilesLines
* Convert Python ports to FLAVORS.Mathieu Arnold2017-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 Notes: svn path=/head/; revision=455210
* Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.Mathieu Arnold2016-04-011-2/+2
| | | | | | | | With hat: portmgr Sponsored by: Absolight Notes: svn path=/head/; revision=412346
* - Convert ports of devel/ to USES=pythonMarcus von Appen2014-10-201-4/+3
| | | | | | | Approved by: portmgr (implicit) Notes: svn path=/head/; revision=371280
* - Stage supportAntoine Brodin2014-01-202-33/+1
| | | | | | | - Use PYDISTUTILS_AUTOPLIST Notes: svn path=/head/; revision=340455
* Give my bzr plugin ports back to pool.Carlo Strub2013-10-051-1/+1
| | | | Notes: svn path=/head/; revision=329496
* Add NO_STAGE all over the place in preparation for the staging support (cat: ↵Baptiste Daroussin2013-09-201-5/+2
| | | | | | | devel part 1) Notes: svn path=/head/; revision=327722
* Bump PORTREVISION to reflect name change from devel/bazaar-ng --> devel/bzrCarlo Strub2012-06-171-2/+3
| | | | Notes: svn path=/head/; revision=299513
* Update to 1.4Carlo Strub2012-02-243-5/+7
| | | | | | | Approved by: glarkin@ (mentor) Notes: svn path=/head/; revision=292181
* Update to 1.3Carlo Strub2011-10-203-8/+11
| | | | | | | Approved by: glarkin@ (mentor) Notes: svn path=/head/; revision=284002
* Change maintainer address to my FreeBSD addressCarlo Strub2011-09-151-1/+1
| | | | | | | Approved by: wen@ (mentor) Notes: svn path=/head/; revision=281802
* The Bazaar pipeline plugin helps you organize your changes intoGreg Larkin2010-11-184-0/+65
sections called "pipes". Pipelines can help you: * focus on each set of changes as a coherent piece, without being distracted by other sets of changes. * respect diff size limits when submitting changes * avoid reviewer fatigue when submitting changes for code review * maintain a set of patches against an upstream branch WWW: http://wiki.bazaar.canonical.com/BzrPipeline PR: ports/152305 Submitted by: Carlo Strub <c-s at c-s.li> Notes: svn path=/head/; revision=264773
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-12 20:44:21 +0000