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

Bug#787298: (no subject)

On 02/06/2015 7:12 AM, "Emmanuel Kasper" <emmanuel@libera.cc> wrote:
> > The other point is that including (either) provisioner takes us further
> > from the standard Debian image.
> BTW, Was is actually a standard Debian image ?
> To the best of my knowledge, I would define it as all the packages with
> Priority: required and important.
> According to the Debian Jessie installation guide [1], the *standard*
> task is also recommended.
> In server/containers environments it makes sense to restrict the list
> of packages installed.
> However the main aim of the Vagrant Virtualbox base boxes,are shareable
> development environments.
> In this kind of setup, I would expect the usual comfort of the debian
> experience, having for instance a mail server to send stuff,
> bash-completion or patch installed, all packages with come with the
> standard priority.
> So I am in favor of installing this task, which will bring aptitude as a
> side effect.
> Concerning the inclusion/removal of providers via specific boxes, why not.
> [1] https://www.debian.org/releases/jessie/i386/apbs04.html.en
> Section: Package selection
Base boxes should be both provisionerless as well as stock as possible.

Vagrant plugins should be used to look after installing provisioners such as your an ansible, puppet etc.

Chef is already doing this where the bento boxes are provisionerless and the vagrant-omnibus plugin installs the version of Chef to your liking.

> --
> To UNSUBSCRIBE, email to debian-cloud-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 556CC9F9.9020508@libera.cc">https://lists.debian.org/[🔎] 556CC9F9.9020508@libera.cc

Reply to: