Puppet Software Collections

Note: This is a proposal, not yet validated by the SIG.

Puppet 4

In order to:

I think we should build a Software Collection to maintain the Puppet 4 packages.


Why is a SCL needed?

Should we build the software collection on top of the Ruby 2.0.0 or 2.2.0?

Should we name the SCL puppet43 puppet4 puppet SCL?

The ideal would be to have the SCL named puppet-pc1 because pc1 is the identifier used by upstream project to identify the puppet 4 release. We could ensure that the content of the SCL == the Repository == The content of the upstream repository.

What would be the path of the SCL?

I think that it should then be /opt/centos/puppet-pc1, /etc/opt/centos/puppet-pc1, /var/opt/centos/puppet-pc1

Should we provide a puppet4 command in the default $PATH?

SpecialInterestGroup/ConfigManagementSIG/Puppet/SoftwareCollections (last edited 2019-12-09 09:11:52 by anonymous)