Bug#787298: (no subject)

[Anders Ingemann <anders@ingemann.de>]

I think we are in need of some kind of policy here.
The idea of those images is that you can download them and they are ready-to-use (which means pre-installing software).

This is in direct conflict with Debian branded images, because we want them to be as close to the standard distribution as possible.

Vagrant supports multiple config management tools - should we split the images up so that there are flavours (including vanilla - nothing pre-installed)? The maintenance effort would of course be multiplied because of that. I don't really have a preference either way, but this is not the first time this challenge has arisen and we might be in need of some general guidelines.

On Sun, May 31, 2015 at 11:30 AM Marcin Kulisz <debian@kulisz.net> wrote:

I think that I won't agree that vagrant default box should include those
packages.

Simple explanations are:

1. it will take us further from standard Debian img
2. Ansible is not the only config mgmt soft which is used and to include at
  least the most popular will bloat base box very significantly (puppet, chef,
  salt, cfengine and more)

So, I'd say keeping those away from base image and allowing users to install
them in their own images is better idea then enforcing one over others or
installing all and having bloated base box.
--

|_|0|_|                                          |
|_|_|0|         "Heghlu'Meh QaQ jajVam"          |
|0|0|0|         -------- kuLa ---------          |

gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3
3DF1 A4DF C732 4688 38BC F121 6869 30DD  58C3 38B3