Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Using bitbake in minimal chroot environment
Date: Mon, 15 Feb 2010 07:24:43 -0800	[thread overview]
Message-ID: <4B79673B.50108@balister.org> (raw)
In-Reply-To: <20100214135613.GF5364@jama>

On 02/14/2010 05:56 AM, Martin Jansa wrote:
> Hi,
>
> I'm just thinking about using bitbake only in minimalistic chroot.
>
> What are advantages/disadvantages?
>
> How I see it:
>
> Advantages:
> 1) more secure (I started to use separate user for bitbake, when I
>     started to play with bitbake master instead release - because that
>     warning it said), but chroot is even better.
> 2) less problems when autotools pick some header or lib from buildhost
>     instead of staging
> 3) easier to check, that -native package is missing for some important
>     lib
>
> Disadvantages:
> 1) Few more MB for building environment (extra libc, gcc, binutils, git,
>     svn, sh, etc. installed in chroot
> 2) More administrative to keep chroot system updated
> 3) harder to check, that autotools won't pick something from buildhost
>     in normal environment before pushing new version/recipe (ie I won't
>     have SDL libs installed in chroot, but everybody else will and maybe
>     build will fail for them after I push some recipe.

I see this as a good thing :)

Philip


>
> If nobody points some big disadvantage I didn't think about, I'll give
> it a try (with precompilled gentoo stage tarball it's task for half an
> hour using cp :)).
>
> Using some sofisticated sandbox setting (as gentoo ebuilds do) would be
> also good alternative, is someone trying that?
>
> Regards,
>



  reply	other threads:[~2010-02-15 15:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 13:56 Using bitbake in minimal chroot environment Martin Jansa
2010-02-15 15:24 ` Philip Balister [this message]
2010-02-15 16:59   ` Frans Meulenbroeks
2010-02-15 17:19     ` Martin Jansa
2010-02-15 17:57       ` Frans Meulenbroeks
2010-02-15 18:12         ` Martin Jansa
2010-02-15 18:22         ` Mike Westerhof
2010-02-15 18:36           ` Martin Jansa
2010-02-15 18:43       ` Koen Kooi
2010-02-15 20:53         ` Frans Meulenbroeks
2010-02-15 22:04         ` Tom Rini
2010-02-15 22:15           ` Koen Kooi
2010-02-16  8:11           ` Koen Kooi
2010-02-18  9:20           ` Marcin Juszkiewicz
2010-02-18  9:43             ` Koen Kooi
2010-02-18 13:30             ` Henning Heinold
2010-02-16 13:52 ` Otavio Salvador
2010-02-17  9:35   ` Martin Jansa

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=4B79673B.50108@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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