* 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)
* remove USE_GROFF to prevent warnings
* fix the examples directory
* use .conf files from upcoming 3.1 version (they work by default and the patches can be easily removed when we upgrade)
* add a default minimal puppet.conf that works instead of the currently broken one we ship
* only include conf files we need
* no need to create the hierarchy under /var/puppet since puppet will take care of it
ok robert@ (maintainer), jasper@
PLIST and delete everything under the @sample'd directory instead of the
directory itself to prevent a warning from pkg_delete(1) trying to
remove a non existing directory and to help preventing left-over files
and directories.
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.
