Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] RFC: Adding Vagrant file for provisioning
Date: Thu, 10 Sep 2015 00:14:56 +0200	[thread overview]
Message-ID: <55F0AF60.7030102@mind.be> (raw)
In-Reply-To: <1441836107-17689-1-git-send-email-angelo.compagnucci@gmail.com>

On 10-09-15 00:01, Angelo Compagnucci wrote:
> This patch adds a Vagrant file to buildroot. With this file
> you can provision a complete buildroot developing environment
> in minutes on all major platforms.
> 
> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
> ---
> 
> This patch is a tentative approach to add a standard and official
> Vagrant file to buildroot. With this file you can setup an isolated
> build environment based on Vagrant on all major platforms.
> 
> The file is fairly basic right now, it sets up correct Ubuntu version
> to download and install required packages for buildroot.
> 
> I'm open to suggestions and critics!

 Here goes:

 If you're already on a platform that runs vagrant, then you have enough to run
buildroot as well, so why would you want to put it inside a VM and double your
build time? Buildroot really really tries very hard to make sure it runs in any
environment, so there should be no need for any of this trickery.

 The only limitation you do have is that you need some tools like a compiler and
some VCSes. If that is what you want to work around, then I'd prefer to go the
way of a single-user nix environment to import these tools.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-09-09 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 22:01 [Buildroot] [PATCH] RFC: Adding Vagrant file for provisioning Angelo Compagnucci
2015-09-09 22:14 ` Arnout Vandecappelle [this message]
2015-09-10  6:15   ` Angelo Compagnucci
2015-09-10  8:07     ` Arnout Vandecappelle
2015-09-10  8:12       ` Angelo Compagnucci
2015-09-10 11:56         ` Nimai Mahajan
2015-09-10 12:13           ` 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=55F0AF60.7030102@mind.be \
    --to=arnout@mind.be \
    --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