From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] support/misc: Adding Vagrant file for provisioning
Date: Sat, 20 Feb 2016 21:19:54 +0100 [thread overview]
Message-ID: <87fuwnf82d.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+TH9VnQB_-2qKy2yRzOT6jCzz5hv4xiioW5r5g8F69G2sgrZg@mail.gmail.com> (Angelo Compagnucci's message of "Sat, 20 Feb 2016 12:07:54 +0100")
>>>>> "Angelo" == Angelo Compagnucci <angelo.compagnucci@gmail.com> writes:
Hi,
> Obviously, I'm not in the position to steer the project in a way or
> another, but IMHO giving a little bit of advice on how to run
> Buildroot on others OSes could only benefit the project as a whole.
> And please stop with that Puppet, Chef and other amenities, they are
> not meant to rapidly build a virtual machine with some software inside
> and nobody talked about them than you.
> As I stated before, the goal here is to give the opportunity to the
> people who cannot run Buildroot natively to use it anyway, in a simple
> to run Vm.
> Nothing more nothing less.
Understood, and I appreciate it. I think the confusion / disagreement
comes from the fact that the main developers aren't the target audience,
and they don't have a need / desire to use it, but that doesn't mean
others might not.
--
Venlig hilsen,
Peter Korsgaard
prev parent reply other threads:[~2016-02-20 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 22:51 [Buildroot] [PATCH v3] support/misc: Adding Vagrant file for provisioning Angelo Compagnucci
2015-12-20 15:28 ` Yann E. MORIN
2016-02-04 16:23 ` Peter Korsgaard
2016-02-05 8:05 ` Angelo Compagnucci
2016-02-20 10:47 ` Yann E. MORIN
2016-02-20 10:57 ` Angelo Compagnucci
2016-02-20 10:56 ` Yann E. MORIN
2016-02-20 11:07 ` Angelo Compagnucci
2016-02-20 20:19 ` Peter Korsgaard [this message]
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=87fuwnf82d.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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