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

[Stig Sandbeck Mathisen]

I've done a test merge and packaging of the new rc of puppet 2.6.0, it
seems to be working fine.

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.

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?  

Or should we, in addition to a puppet package, provide service packages
with just init scripts and the compatbility executables?

--
Stig Sandbeck Mathisen
                      ooo, shiny!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20100713/6655e9b4/attachment.pgp>