[Buildroot] Tesla is using Buildroot

[Adrian Perez de Castro]

On Fri, 11 May 2018 22:42:45 -0300 (BRT), Carlos Santos <casantos at datacom.ind.br> wrote:
> > From: "ratbert90" <aduskett at gmail.com>
> > To: anisse at astier.eu, "Thomas Petazzoni" <thomas.petazzoni at bootlin.com>
> > Cc: "Olof Johansson" <olof at lixom.net>, buildroot at uclibc.org
> > Sent: Friday, May 11, 2018 10:22:49 PM
> > Subject: Re: [Buildroot] Tesla is using Buildroot
> >
> > [...]
> >
> > - there's a tesla-verity package which seems to be a custom init that
> > checks the validity of the verity metadata and interacts with
> > firmware to check soc lock status before calling dmsetup.
> > - there are a few packages that look like backports: python-dateutil,
> > nanomsg, python-pytz, python-jsonschema
> > - tesla-binutils is a "real" host binutils (non-cross)
> > - there's tesla-libsystemd stub that builds a libsystemd with stubbed
> > functions
> 
> Makes me wonder why they don't use a BR2_EXTERNAL.

Probably because (AFAIK) it is not yet possible to override base package in
a BR2_EXTERNAL. I have tripped on this myself a couple of times, and ended
up providing a top-level Makefile in the repo for my BR2_EXTERNAL which
downloads a certain version of the Buildroot tarball and applies a couple
of patches over it, then proceeds to chain up to the Buildroot Makefiles
passing the path BR2_EXTERNAL path down to them (so from the point of view
of somebody building, they just download the BR2_EXTERNAL repo and do “make
foo_defconfig && make”).

It would be great to allow overriding base packages in a BR2_EXTERNAL 🤔

Cheers,


--
 Adrián 🎩
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180512/cfb2c8e2/attachment-0002.asc>