Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-09-13
Date: Sat, 14 Sep 2013 19:00:42 +0200	[thread overview]
Message-ID: <20130914190042.4b6f0833@skate> (raw)
In-Reply-To: <523481F4.7000304@googlemail.com>

Dear Carsten Schoenert,

On Sat, 14 Sep 2013 17:34:12 +0200, Carsten Schoenert wrote:

> In Debian we use sbuild (Perl), cowbuilder (ELF executable) / pbuilder
> (shell) to set up a clean basic chroot and after that clone this base
> chroot and build the *.deb packages inside. The core chroot is setted up
> by calling debootstrap for the target platform.
> 
> Maybe you want to look at it and can grap something?
> I just use the tools, Perl isn't my favorite language and pbuilder just
> works as expected, so don't ask me anything special. *g*
> 
> I personally use pbuilder, it's just a shell script with soem external
> calls, there should be something suitable I think.

Thanks for the suggestion. It happens that almost 10 years ago, I did a
bit of Debian packaging, and I was a user of pbuilder to isolate the
build process in a chroot.

It could indeed be useful for others to reproduce builds in a minimal
chroot, but for the autobuilder servers themselves it's not very
useful. pbuilder is mainly useful when you need to create a different
chroot everytime you want to build a package (the chroot should have
the build dependencies installed). While with Buildroot, the set of
core dependencies to be installed is always the same. So what happens
in my autobuilder machine is that I have one static chroot, in which all
the builds are done.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-09-14 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-09-13 Thomas Petazzoni
2013-09-14 12:36 ` Michael Rommel
2013-09-14 13:19   ` Stephan Hoffmann
2013-09-14 15:03   ` Thomas Petazzoni
2013-09-14 15:16     ` Michael Rommel
2013-09-14 15:34     ` Carsten Schoenert
2013-09-14 17:00       ` Thomas Petazzoni [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=20130914190042.4b6f0833@skate \
    --to=thomas.petazzoni@free-electrons.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