They'll be named 'puppet-agent' and therefore won't auto-upgrade if you already have puppet installed. I mentioned this up-thread but I can't blame you for missing it :)
On Nov 24, 2014, at 1:02 PM, Joachim Thuau <e...@korigan.net> wrote: > on a slightly different tangent: > > Would it be possible to get the puppet 4.x packages named "puppet4" instead > of puppet? This would allow for one to ensure that bug fixes for puppet 3.x > would be installed as soon as they become available for those of us sticking > with 3.x, even after the 4.x release, without forcing the upgrade to 4.x > right away. (I, for one, have a lot of work to make that transition > possible). > > To me, this looks a lot like the apache1/apache2 upgrade path, years ago, > where users were given a choice of which one they wanted to install, but > still provide an upgrade path for "fixes" after the apache2 release for the > original apache1x version. > > Any strong opinions out there? > > Jok Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 puppet platform // coffee // techno // bicycles -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/E89B6391-61F8-4664-ACEF-F03492132FD7%40puppetlabs.com. For more options, visit https://groups.google.com/d/optout.
