[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#787298: (no subject)

Den 2 jun 2015 13:51 skrev "Marcin Kulisz" <debian@kulisz.net>:
> On 2015-06-02 20:14:19, Chris Fordham wrote:
> > On Tue, Jun 2, 2015 at 7:59 PM, Martey Dodoo <bugs.debian.org@marteydodoo.com>
> > wrote:
> >     Personally, I think that if third-party software like Chef or Puppet are
> >     installed in the base box (with all of their dependencies), it also makes
> >     sense to install aptitude so that upgrading packages with Ansible works
> >     properly.
> I see no sense in installing aptitude to upgrade packages when apt-get is
> already there. I just had a quick look into ansible apt module and have to say
> it's a bit messy. It's utilising apt-get for dist-upgrade and aptitude for
> full-upgrade. Probably this should be pointed out to ansible devs as suboptimal
> solution.

Well, isn't aptitude installed by default by Debian?  I remember aptitude being recommended before apt-get, at least previously, by Debian. So I don't see any problems with that.

> >  Thats unfortunate, we need to fix this and make them provisionerless and get
> > rid of the 'enhancement' approach. Vagrant plugins and inline provisioning
> > is the right way to do it (as demonstrated by Chef Software Inc.).
> I agree.

Yes, it's easier to add packages then to remove.

Reply to: