On Thursday, June 18, 2015 at 4:18:37 PM UTC-7, Ken Bowley wrote: > > This is better than what is currently being used, but I'm strongly in the > AIO idea to be stupid. Split it into multiple packages and use proper > dependencies like every other sane packaging system has done for a long, > long time. > > If all you do is bump the version of facter, then only have me download > and install the meta package that depends on the new facter, and the new > facter package, not everything. > > > Agree. Thought I'd chime in (late) as the original poster.
Versioning starting with 4.x is a good start, but I still think your AIO approach is wrong. Have collector rpms that 'require' the pieces of the puzzle and package hiera/etc. in individually bundled standalone packages. If you do that: - you can keep versioning facter to 2.x.y if you want - you can keep versioning puppetserver any way you want - and just version the collection (bundle, pick a term) with the 4.x.x identifier you want to publicize as release-4.x.x To update the client, 'yum update puppet' and have it update the sub-pieces it needs (hiera/mco/etc.) To update the server, 'yum update puppetserver' and have it do the server piece. Lastly, if it's me, I would not bundle the agent/client stuff 'in' the puppetserver package. I would 'require' the client-stuff to be co-installed with the server stuff using the packaging mechanisms the os providers already give you. (in other words, release 'empty' rpms that require x and y and z - works great if you don't cause dependency hell by getting too fancy) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/04f724ea-b55f-4ba8-a96e-35a580c6c31a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
