From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add libvirt (KVM) support
Date: Mon, 27 May 2019 09:04:52 +0200 [thread overview]
Message-ID: <20190527090452.6124a023@windsurf> (raw)
In-Reply-To: <CA+_SqVY2wACSL=-5rugRsL0O+kKJqHnqgSzc1ouuy=9gcoRDjQ@mail.gmail.com>
Hello,
On Sun, 26 May 2019 22:14:54 +0200
Angelo Compagnucci <angelo@amarulasolutions.com> wrote:
> The only thing that bothers me is that the debian images for vagrant
> are not official and only maintained by a single person
> (https://app.vagrantup.com/debian).
> On the contrary, Ubuntu images are officially maintained by canonical
> into their efforts for ubuntu on cloud.
>
> Alternatively we can switch to Fedora which is officially supported
> and supports libvirt, but we have to completetly rewrite the provision
> section of the vagrantfile.
Do we really need to make a choice here ?
For Docker, our intention is to have several Dockerfiles for different
distributions, in support/docker/.
What about having several Vagrantfiles, in support/vagrant/, also to
support different distributions ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-27 7:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 17:36 [Buildroot] [PATCH 1/1] Add libvirt (KVM) support Christopher Peeters
2019-04-13 20:21 ` Thomas Petazzoni
2019-04-15 7:46 ` Christopher Peeters
2019-04-15 12:23 ` Arnout Vandecappelle
2019-04-15 14:06 ` Angelo Compagnucci
2019-04-15 14:54 ` Christopher Peeters
2019-05-13 11:34 ` Christopher Peeters
2019-05-26 13:21 ` Arnout Vandecappelle
2019-05-26 20:14 ` Angelo Compagnucci
2019-05-26 21:30 ` Arnout Vandecappelle
2019-05-27 7:04 ` Thomas Petazzoni [this message]
2019-05-27 7:24 ` Angelo Compagnucci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190527090452.6124a023@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox