[Pkg-puppet-devel] Structural changes in the puppet packaging

[Mathias Gug]

Hi,

Excerpts from Stig Sandbeck Mathisen's message of Tue Jul 13 11:51:02 +0200 2010:
> 
> Puppet has moved to a "single executable with argument" style, much like
> debhelper and git, while retained the old executables as compatbility
> wrappers.
> 
> In my test packaging, I've moved "/usr/bin/puppet" and and puppet(8) to
> the "puppet-common" package.
>

Seems like the best option to me in order to try to minimize package
renaming.

> However:
> 
> There are large structural changes in puppet with the soon-to-be 2.6.0
> release:
> 
> ,----
> | puppetmasterd > puppet master
> | puppetd       > puppet agent
> | puppet        > puppet apply
> | puppetca      > puppet cert
> | ralsh         > puppet resource
> | puppetrun     > puppet kick
> | puppetqd      > puppet queue
> | filebucket    > puppet filebucket
> | puppetdoc     > puppet doc
> | pi            > puppet describe
> `----
> 
> The "puppet" and "puppetmaster" packages will eventually end up with
> very little else than the service init scripts of upstart jobs.
> 
> Should this be reflected in the package names?  Should these packages be
> renamed "puppet-agent" and "puppet-master"?
> 
> Should we relayout the packaging again, pull everything into the
> "puppet" package again, and have init scripts and upstart jobs in that
> package for the agent, master, and queue daemons?  
>

I would suggest moving everything in puppet-common and have the existing
puppet and puppetmaster packages (as well as a new puppetqd package)
provide init scripts and relevant compatibility wrappers.

-- 
Mathias Gug
Ubuntu Developer  http://www.ubuntu.com