openbsd-ports/sysutils/ruby-puppet/Makefile

# $OpenBSD: Makefile,v 1.57 2016/09/06 11:14:51 jasper Exp $

    SUBDIR =
    #SUBDIR += 3
    SUBDIR += 4

.include <bsd.port.subdir.mk>
stop building puppet 3, effectively making puppet 4 the default on OpenBSD. puppet 3 is scheduled to be removed from the tree after 6.1. for more information on migrating to Puppet 4, please refer to [1] as a starting point. however note we don't have a port for puppetserver yet, it's a work in progress, see upstream SERVER-14 for more information. However the ruby puppetmaster still works fine for us. 1: https://docs.puppet.com/puppet/latest/reference/upgrade_major_pre.html as discussed with and OK sebastia@ 2016-09-06 11:14:51 +00:00			`# $OpenBSD: Makefile,v 1.57 2016/09/06 11:14:51 jasper Exp $`
import of ruby-puppet-0.20.1: Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files. Puppet's simple declarative specification language provides powerful classing abilities for drawing out the similarities between hosts while allowing them to be as specific as necessary, and it handles dependency and prerequisite relationships between objects clearly and explicitly. Puppet is written entirely in Ruby. 2007-01-03 10:01:47 +00:00
Split ruby-puppet: * move the current port to ruby-puppet/3 * add a new puppet-2.7.X port under ruby-puppet/2 This allows us to ship with 2 different versions of Puppet. Since the Enterprise version is still running 2.7, we want to have a matching client because running puppet3 against a puppet2 server is highly discouraged and will mostly no work correctly. ok jasper@, robert@ (maintainer) 2013-03-08 16:12:47 +00:00			`SUBDIR =`
stop building puppet 3, effectively making puppet 4 the default on OpenBSD. puppet 3 is scheduled to be removed from the tree after 6.1. for more information on migrating to Puppet 4, please refer to [1] as a starting point. however note we don't have a port for puppetserver yet, it's a work in progress, see upstream SERVER-14 for more information. However the ruby puppetmaster still works fine for us. 1: https://docs.puppet.com/puppet/latest/reference/upgrade_major_pre.html as discussed with and OK sebastia@ 2016-09-06 11:14:51 +00:00			`#SUBDIR += 3`
hookup puppet 4. it appears to be working well for agents and webrick masters. ok aja@ 2016-06-01 09:11:24 +00:00			`SUBDIR += 4`
import of ruby-puppet-0.20.1: Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files. Puppet's simple declarative specification language provides powerful classing abilities for drawing out the similarities between hosts while allowing them to be as specific as necessary, and it handles dependency and prerequisite relationships between objects clearly and explicitly. Puppet is written entirely in Ruby. 2007-01-03 10:01:47 +00:00
Split ruby-puppet: * move the current port to ruby-puppet/3 * add a new puppet-2.7.X port under ruby-puppet/2 This allows us to ship with 2 different versions of Puppet. Since the Enterprise version is still running 2.7, we want to have a matching client because running puppet3 against a puppet2 server is highly discouraged and will mostly no work correctly. ok jasper@, robert@ (maintainer) 2013-03-08 16:12:47 +00:00			`.include <bsd.port.subdir.mk>`