notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: sysutils/bsdploy/Makefile

Number of commits found: 14

Saturday, 18 May 2019
12:40 koobs search for other commits by this committer
sysutils/bsdploy: Update to 2.3.0

Changelog:

  https://github.com/ployground/bsdploy/blob/2.3.0/CHANGES.rst
Original commitRevision:501961 
Wednesday, 20 Jun 2018
17:05 mat search for other commits by this committer
Use PY_FLAVOR for dependencies.

FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight
Original commitRevision:472884 
Thursday, 30 Nov 2017
15:50 mat search for other commits by this committer
Convert Python ports to FLAVORS.

  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
Original commitRevision:455210 
Thursday, 16 Mar 2017
19:23 antoine search for other commits by this committer
Rename python setuptools ports to better match other python ports

Reviewed by:	mat, sunpoet
With hat:	portmgr
Differential Revision:	https://reviews.freebsd.org/D9983
Original commitRevision:436290 
Friday, 1 Apr 2016
14:25 mat search for other commits by this committer
Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.

With hat:	portmgr
Sponsored by:	Absolight
Original commitRevision:412349 
Monday, 30 Nov 2015
08:37 koobs search for other commits by this committer
archivers/py-liblzma: Rename to pylibzma, Modernize

- Rename to match upstream (PyPI) name: pylibzma
- Backport upstream issue/commit to fix build without pkg-config [1][2]
- Remove post-patch: target, no longer necessary
- Remove other setup.py overrides, back to upstream sources
- Add do-test target:
- Add LICENSE_FILE
- Add MOVED entry

While I'm here:

- Update sysutils/bsdploy dependency

[1] https://bugs.launchpad.net/pyliblzma/+bug/613837
[2] https://bazaar.launchpad.net/~proyvind/pyliblzma/trunk/revision/494

Reviewed by:		sbz
Approved by:		dbn (maintainer timeout, 15 days)
Differential Revision:	D4161
Original commitRevision:402654 
Wednesday, 28 Oct 2015
14:39 koobs search for other commits by this committer
sysutils/bsdploy: Update to 2.1.0

- Update PORTVERSION and distinfo checkum (2.1.0)
- Update RUN_DEPENDS versions
- Add NO_ARCH
- Remove pytest.ini which forces pep8 and flakes for tests

Changes:

  https://github.com/ployground/bsdploy/blob/master/CHANGES.rst
Original commitRevision:400397 
Friday, 6 Mar 2015
01:07 koobs search for other commits by this committer
sysutils/bsdploy: Update to 2.0.0

- Update to 2.0.0
- Use PORTVERSION over DISTVERSION
- Update minimum RUN_DEPENDS versions
- Seperate OPTIONS from OPTIONS_DESC's

Changes: 2.0.0 - 2015-03-05

  * Add support for http proxies
  * Deactivate pkg's auto update feature by default
  * Add support for firstboot-freebsd-update (disabled by default)
  * [BACKWARDS INCOMPATIBLE] switched from ipfilter to pf
    Note: you MUST convert any existing ipnat_rules to the new pf_nat_rules.
  * Provide defaults for VirtualBox instances (less boilerplate)
  * Set full /etc/ntp.conf instead of trying to fiddle with an existing one.
  * Support configuration as non-root user (Issue #62)
  * Switched to semantic versioning (see http://semver.org)
Original commitRevision:380572 
Wednesday, 18 Feb 2015
22:34 koobs search for other commits by this committer
sysutils/bsdploy: Mark UnBROKEN

Mark no longer BROKEN as ploy_ansible has grown support for
Ansible > 1.8 [1] and is now in the ports tree [2].

Thank you Tom Lazar and Florian Schulze for the extremely responsive support
and fix.

[1] https://github.com/ployground/ploy_ansible/pull/13
[2] https://svnweb.freebsd.org/changeset/ports/379322
Original commitRevision:379325 
11:32 koobs search for other commits by this committer
sysutils/bsdploy: Mark BROKEN

Mark BROKEN temporarily since ploy_ansible doesnt play nice with
Ansible >= 1.8 [1] and our sysutils/ansible port is at 1.8.3.

[1] https://github.com/ployground/bsdploy/issues/60

Reported by:    dlangille
Original commitRevision:379205 
Saturday, 31 Jan 2015
00:01 koobs search for other commits by this committer
sysutils/bsdploy: Update to 1.3

- Update bsdploy to 1.3
- Update all py-ploy[_]* dependencies:

    ploy:         1.0.3
    ploy_ensible: 1.2.1
    ploy_ec2:     1.1.1
    ploy_ezjail:  1.1.0
    ploy_fabric   1.1.0

- Sort USE_PYTHON's

Changes:

  * bsdploy:      https://github.com/ployground/bsdploy/blob/1.3/CHANGES.rst
  * ploy:         https://github.com/ployground/ploy/blob/1.0.3/HISTORY.rst
  * ploy_ansible:
https://github.com/ployground/ploy_ansible/blob/1.2.1/HISTORY.rst
  * ploy_ec2:     https://github.com/ployground/ploy_ec2/blob/1.1.1/HISTORY.rst
  * ploy_ezjail: 
https://github.com/ployground/ploy_ezjail/blob/1.1.0/HISTORY.rst
  * ploy_fabric: 
https://github.com/ployground/ploy_fabric/blob/1.1.0/HISTORY.rst
Original commitRevision:378188 
Friday, 24 Oct 2014
16:56 mva search for other commits by this committer
- Convert ports of sysutils/ to new USES=python

Approved by:	portmgr (implicit)
Original commitRevision:371454 
Monday, 21 Jul 2014
13:19 koobs search for other commits by this committer
sysutils/bsdploy: Update to 1.0.0 !! #GOLD

Update BSDploy and plugins to the latest, greatest, stable and gold 1.0.0
release while @tomlazar and @fschulze are running BSDploy training at
EuroPython 2014 :D

- Update RUN_DEPENDS to require >= 1.0.0 for all plugins
Original commitRevision:362434 
Tuesday, 8 Jul 2014
14:30 koobs search for other commits by this committer
[NEW] sysutils/bsdploy: Container Management for FreeBSD Jails

BSDploy is a comprehensive tool to provision, configure and maintain
FreeBSD jail hosts and jails.

Its main design goal is to lower the barrier to repeatable jail setups.

  * Modular provisioning with plugins for VirtualBox, Amazon EC2 and
    an achitecture to support more.
  * Bootstrap complete jail hosts from scratch.
  * Declarative configuration: All hosts and their properties defined
    in ploy.conf are automatically exposed to Ansible.
  * Imperative maintenance: Run Fabric scripts with ploy do JAILNAME
    TASKNAME and have all of the hosts and their variables in fab.env.
  * Configure ZFS pools and filesystems with whole-disk-encryption.

WWW: http://docs.bsdploy.net/
Original commitRevision:361248 

Number of commits found: 14