[Pkg-puppet-devel] Plans for packaging puppet 6

[Gabriel Filion]

Hello,

On 2020-05-08 4:08 p.m., Thomas Goirand wrote:
> I wonder what the plans for packaging Puppet 6 are, and how I can help.
> Is there anyone already working on this?

I'm not aware of whether or not any work has already planned/done in
this direction.
Thanks for getting this conversation going since it will be important to
have a more recent version of puppet in debian before the next release
reaches a freeze.
e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950182


From what I know, packaging puppet 6 can be broken down into three
parallel efforts, the biggest one being figuring things out for the
Clojure codebase: puppetserver, puppet-agent and facter.


Puppet 6 has moved on to a Clojure-based puppetmaster (now called
puppetserver). So we'd need to package this clojure codebase and all of
the missing required Clojure libraries. So I guess this means first
figuring out what all of the dependencies are and which ones are
missing. I unfortunately have 0 knowledge about how to package Clojure
code :\
https://github.com/puppetlabs/puppetserver

This might be a good starting point for finding out puppetserver's
dependencies:
https://github.com/puppetlabs/puppetserver/blob/master/project.clj#L33


The agent code is still a ruby codebase. Should this be packaged as
"puppet-agent" in debian to clarify that it's using the new agent codebase?
https://github.com/puppetlabs/puppet-agent


facter had a short portion of life as a C++ binary but as far as I
understand it version 4.x is back to a ruby codebase again
https://github.com/puppetlabs/facter-ng


both puppet-agent and facter-ng seem to depend on puppet-runtime
(according to the readme) which itself seems to need vanagon.. however,
this seems to be used for creating an omnibus package that contains
openssl, ruby and all of the required runtime. so it might be possible
that this part of the build is not necessary? I haven't looked into how
tightly knit into build this thing really is. Maybe just packaging the
ruby gems for puppet-agent and facter-ng (which I reckon could keep the
name "facter" to avoid useless churn) would be enough for our purpose.
https://github.com/puppetlabs/puppet-runtime
https://github.com/puppetlabs/vanagon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-puppet-devel/attachments/20200508/f4f2e1a9/attachment.sig>