FreeBSD ports tree https://cgit-dev.freebsd.org/ports/atom?h=2018Q1 2017-12-19T14:58:15Z 2017-12-19T14:58:15Z Nikolai Lifanov lifanov@FreeBSD.org 2017-12-19T14:58:15Z urn:sha1:5d36ee1c3632642f638a85f6740b51db2ef8449b Changes: https://github.com/docker/compose/blob/1.18.0/CHANGELOG.md 2017-11-30T15:50:30Z Mathieu Arnold mat@FreeBSD.org 2017-11-30T15:50:30Z urn:sha1:551be3c7231225ed9c26479af2b8914fb2ef0ea8 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 2017-11-10T19:16:29Z Nikolai Lifanov lifanov@FreeBSD.org 2017-11-10T19:16:29Z urn:sha1:d0be8901040818b7cd513c926f2f2686852a9f51 Changes: https://github.com/docker/compose/blob/1.17.1/CHANGELOG.md 2017-11-03T17:35:00Z Nikolai Lifanov lifanov@FreeBSD.org 2017-11-03T17:35:00Z urn:sha1:e60a60c19b64aab8b484fc6c62f740f0aa2593d4 Changes: https://github.com/docker/compose/blob/1.17.0/CHANGELOG.md 2017-09-05T13:31:26Z Nikolai Lifanov lifanov@FreeBSD.org 2017-09-05T13:31:26Z urn:sha1:4bc71e288cfda751451b5dc8d836ded665c63945 2017-08-23T16:44:23Z Nikolai Lifanov lifanov@FreeBSD.org 2017-08-23T16:44:23Z urn:sha1:bc1c316b67f73393384f4310bb616769ac4e075d Make setup.py satisfiable by API-compatible versions we have in ports. References: https://github.com/docker/compose/issues/4848 https://bugzilla.redhat.com/show_bug.cgi?id=1452999 PR: 221744 Reported by: decke 2017-07-27T12:54:59Z Nikolai Lifanov lifanov@FreeBSD.org 2017-07-27T12:54:59Z urn:sha1:d846b32a565ae738a8980ae20f61bc751d0d4ee0 Changes: https://github.com/docker/compose/releases/tag/1.15.0 2017-06-20T13:19:55Z Nikolai Lifanov lifanov@FreeBSD.org 2017-06-20T13:19:55Z urn:sha1:74905aaa5f550f29d2bea06b6829ee6f5e0dae19 Changes: https://github.com/docker/compose/releases/tag/1.14.0 2017-05-03T15:47:20Z Nikolai Lifanov lifanov@FreeBSD.org 2017-05-03T15:47:20Z urn:sha1:9faee6b101ed76b555149d24272cd7b9e548133f ### Breaking changes - `docker-compose up` now resets a service's scaling to its default value. You can use the newly introduced `--scale` option to specify a custom scale value ### New features #### Compose file version 2.2 - Introduced version 2.2 of the `docker-compose.yml` specification. This version requires to be used with Docker Engine 1.13.0 or above - Added support for `init` in service definitions. - Added support for `scale` in service definitions. The configuration's value can be overridden using the `--scale` flag in `docker-compose up`. Please note that the `scale` command is disabled for this file format #### Compose file version 2.x - Added support for `options` in the `ipam` section of network definitions 2017-04-19T15:37:04Z Nikolai Lifanov lifanov@FreeBSD.org 2017-04-19T15:37:04Z urn:sha1:ec30fd6508c1130bcfe0e19f098c3aed2e7ea440 Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a Compose file to configure your application's services. Then, using a single command, you create and start all the services from your configuration.