Hi,

attached tarballs contain ports for puppet5 and puppetdb5, they'll be placed 
similar to their 4.X versions, in databases/puppetdb5
as well as sysutils/ruby-puppet/5

So far works for me. I run puppet 5 master behind unicorn/nginx, puppet 4 and 5 
agents seem to work against it.
Haven't tested puppet 3 agents against the master, don't have those around 
anymore.
Puppetboard seems to work against the puppetdb5 as well.

package upgrading from installed puppetdb or puppet is taken care with @pkgpath 
markers.

when these get in, I'd also remove the long time disabled databases/puppetdb as 
well as sysutils/ruby-puppet/3

can keep the puppet and puppetdb 4.X versions around for a while to provide 
both versions of these packages,
alternatively just disable these from building packages and only keep them 
around in the ports tree for a while.
Any preferences about that? if it was me, I'd disable building the 4.X versions 
;)

Test reports, comments, OK etc. welcome ;)

cheers,
Sebastian

Attachment: puppet5.tar.gz
Description: GNU Zip compressed data

Attachment: puppetdb5.tar.gz
Description: GNU Zip compressed data

Reply via email to