From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Introducing new package type, side to side with generic-package
Date: Sat, 2 Nov 2013 11:35:35 +0100 [thread overview]
Message-ID: <20131102113535.685db8fc@skate> (raw)
In-Reply-To: <CAAXf6LWqFR1mPtJ=w8g73R7Ut7m0wxPu_kwgn=ODW1axBx06uQ@mail.gmail.com>
Dear Thomas De Schampheleire,
On Sat, 2 Nov 2013 11:27:12 +0100, Thomas De Schampheleire wrote:
> The problem with buildroot forks is that many good developments in
> these forks do not flow back into the mainline buildroot. This is not
> only disadvantageous for mainline buildroot, but also for the fork
> that has to keep up-to-date with developments in mainline buildroot.
I fully agree.
> To the community: I was going to propose to create a github mirror for
> buildroot to clarify which is the upstream project, but it seems one
> already exists:
> https://github.com/buildroot/buildroot
Yes. I did create this one, and I try to keep it updated from time to
time. I pushed the latest Buildroot version to it yesterday.
> If I search on github for 'buildroot', I get 227 repository results :-(
> Some are just personal repositories, but others are actual forks, like:
>
> Amlogic-related:
> https://github.com/Pivosgroup/buildroot-linux
> https://github.com/vDorst/buildroot
>
> Raspberry Pi:
> https://github.com/nezticle/RaspberryPi-BuildRoot
> https://github.com/gamaral/rpi-buildroot
> https://github.com/huceke/buildroot-rbp
> https://github.com/albertd/buildroot-rpi
>
> GCW0 (open-source gaming console)
> https://github.com/gcwnow/buildroot
>
> BeagleBoard/BeagleBone:
> https://github.com/nerves-project/bbone-erlang-buildroot
> https://github.com/MaxGalemin/buildroot
>
> Maybe we should add something to the website or README regarding
> forks, something saying that we strongly discourage that and are in
> general open in accepting board support in mainline buildroot. But
> what do we do with all the defconfigs and supporting files. I think
> there was some discussion at BDD about that, but I didn't follow it
> well.
There wasn't discussion about this at the latest BDD, but we indeed
discussed it at the FOSDEM 2013 Buildroot Developer Day. See
http://elinux.org/Buildroot:DeveloperDaysFOSDEM2013.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-02 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 19:26 [Buildroot] Introducing new package type, side to side with generic-package Stanislav Vlasic
2013-11-01 21:09 ` Thomas De Schampheleire
2013-11-02 1:46 ` Stanislav Vlasic
2013-11-02 10:27 ` Thomas De Schampheleire
2013-11-02 10:35 ` Thomas Petazzoni [this message]
[not found] ` < CADYw_JJuE71mqxSmQtT1JKLN7d0apTS=DAz+KD7of7n3sVsWnw@mail.gmail.com>
[not found] ` < CAAXf6LWqFR1mPtJ=w8g73R7Ut7m0wxPu_kwgn=ODW1axBx06uQ@mail.gmail.com>
2013-11-02 11:39 ` Stanislav Vasic
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=20131102113535.685db8fc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.