All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ludovic Desroches <ludovic.desroches@microchip.com>
To: buildroot@busybox.net
Subject: [Buildroot] external, how to achieve our needs?
Date: Wed, 26 Feb 2020 14:20:57 +0100	[thread overview]
Message-ID: <20200226132057.zs2lgpm3bkwtjmj2@M43218.corp.atmel.com> (raw)
In-Reply-To: <87imjtoqpr.fsf@tarshish>

Hi Baruch,

On Wed, Feb 26, 2020 at 07:36:00AM +0200, Baruch Siach wrote:
> Hi Ludovic,
> 
> On Tue, Feb 25 2020, Ludovic Desroches wrote:
> > I would like to emphasize that recent changes in buildroot make us
> > think that it won't be easy to get rid of buildroot-at91: devmem2
> > deprecated, rgnd which increases the boot time since it uses the lib
> > jitterentropy, curl library name change and others.
> 
> The curl library name has not changed in the last few year. Do you refer
> to the curl binary Kconfig symbol name change (commit 2a057339cc12)? How
> does that affect your use case? Do you need to support several Buildroot
> versions in a single config?

Yes, that's the Kconfig symbol.

That's one of the pending question, is it possible to support different
versions of Buildroot. When we start using the external, one benefit we had
in mind was we won't have to check/update the external at each new release
of Buildroot. It seems we were wrong, it could only save us to rebase
patches in comparison to the buildroot fork solution.

Regards,

Ludovic

> 
> baruch
> 
> --
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2020-02-26 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 15:01 [Buildroot] external, how to achieve our needs? Ludovic Desroches
2020-02-26  5:36 ` Baruch Siach
2020-02-26 13:20   ` Ludovic Desroches [this message]
2020-02-26 12:11 ` Mircea GLIGA
2020-02-26 13:29   ` Ludovic Desroches
2020-02-26 15:14     ` Peter Korsgaard
2020-02-26 21:59       ` Vadim Kochan
2020-02-26 13:30 ` Mircea GLIGA

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=20200226132057.zs2lgpm3bkwtjmj2@M43218.corp.atmel.com \
    --to=ludovic.desroches@microchip.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.