From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and PTXDist
Date: Thu, 3 Jan 2013 11:08:19 +0100 [thread overview]
Message-ID: <20130103110819.77f4326f@skate> (raw)
In-Reply-To: <CAKvQZ_3=JY06hrgjn2ivcZonpmQ7sHgYX1vwEdda7HPU9k=Bbg@mail.gmail.com>
Dear Willy Lambert,
On Thu, 3 Jan 2013 10:06:35 +0100, Willy Lambert wrote:
> could someone help me in finding what's different between Buildroot
> and PtxDist ? Both project seems active and both projects seems to do
> the same thing (creating the rootfs from scratch) and AFAIK PTXDist in
> a fork from buildroot.
I don't know enough of PTXdist to make an objective and honest
comparison being both projects.
However, I am not sure PTXdist is really a fork of Buildroot. It
certainly uses the same kconfig interface, and also uses make, but
besides that, I am not sure that the PTXdist developers started off
from Buildroot.
In term of activity:
* In 2011, 1093 commits in PTXdist, 1422 commits in Buildroot
* In 2012, 1383 commits in PTXdist, 2645 commits in Buildroot
A difference is that Buildroot is very community-driven, while PTXdist
is driven by Pengutronix, and the vast majority of the contributions are
done by Pengutronix engineers. In the 2476 commits of the last two years
of development, 2116 were done by Pengutronix engineers.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-01-03 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 9:06 [Buildroot] Buildroot and PTXDist Willy Lambert
2013-01-03 10:08 ` 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=20130103110819.77f4326f@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