[Pkg-puppet-devel] Bug#798636:

[Stig Sandbeck Mathisen]

Michael Stahnke <stahnma at puppet.com> writes:

> FWIW, You can run puppet4 under MRI/passenger as the server. I
> wouldn't recommend it, but it is possible.

It seems to be working.

> As for the filesystem pathing, yes the projects have been updated to
> our newer standard paths, but in most cases that a pretty simple patch
> (or will fall back) to the layout debian may expect.

The "where in the world is puppet.conf" case does not seem to be one of
these.

The provided install.rb does take a --configdir argument, among others,
but those do not seem to affect the paths used by the installed
software, only where the software is actually installed.


A small status update on the puppet 4 packaging.

I've got puppet 4 packaged, and it works if I use
"/etc/puppetlabs/puppet/puppet.conf" as the configuration file path.
Some patching is required to use /etc/puppet/puppet.conf.  Instances of
/etc/puppetlabs/ ~/.puppetlabs and /opt/puppetlabs are hardcoded in
places instead of using a configuration method.


After thinking about it for a bit, I've taken the liberty of adjusting
the package names, so they do not reflect the state of puppet version
0.24, plus all the functionality added after that.

New package names, are:

* puppet (all the software.)

* puppet-agent (package containing just the init script and systemd unit
  for the puppet agent.  This package is possibly redundant.)

* puppet-master (init script and systemd unit for starting a single
  master.  This package is possibly redundant.)

* puppet-master-passenger (This package sets depends on apache httpd,
  and configures a puppet master using mod_passenger.  Due to the
  dependency on apache httpd, I'd like to keep this as a separate
  package)

The activerecord storedconfigs patch which was contributed for puppet
3.x has been removed, there does no longer seem to be any code for it to
patch.  If someone still wants to contribute and maintain it, it would
make sense as a separate package containing a terminus or extension for
puppet.  I've no idea if this would _actually_ work.

The editor support packages, puppet-el and vim-puppet, will no longer
use the "puppet" upstream repository and source package, they now have
separate repositories and multiple implementations.

PuppetDB and Puppet Server need a lot of infrastructure and dependencies
packaged.  Leiningen (clojure build system) was recently removed from
Debian, but someone is working on reintroducing it again.
(https://bugs.debian.org/819811)

-- 
Stig Sandbeck Mathisen <ssm at debian.org>