freebsd/ports
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
385,967 Commits 2 Branches 0 Tags
Commit Graph

9 Commits

Author SHA1 Message Date
Kubilay Kocak
892f21154b 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
 2015-11-30 08:37:38 +00:00
Kubilay Kocak
a8f51ee484 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
 2015-10-28 14:39:02 +00:00
Kubilay Kocak
b34b1be785 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)
 2015-03-06 01:07:06 +00:00
Kubilay Kocak
7fd258c31d 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
 2015-02-18 22:34:25 +00:00
Kubilay Kocak
7427785855 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
 2015-02-18 11:32:22 +00:00
Kubilay Kocak
46d3214b70 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
 2015-01-31 00:01:50 +00:00
Marcus von Appen
fae188751b - Convert ports of sysutils/ to new USES=python 
Approved by:	portmgr (implicit)
 2014-10-24 16:56:10 +00:00
Kubilay Kocak
7b01835678 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
 2014-07-21 13:19:24 +00:00
Kubilay Kocak
2d179c00df [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/
 2014-07-08 14:30:27 +00:00