Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Michael Nosthoff <buildroot@heine.tech>, buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC 2/2] docs/manual/migrating.txt: add "individual packages" section
Date: Tue, 3 Aug 2021 23:35:23 +0200	[thread overview]
Message-ID: <20210803233523.5e2b7ff6@windsurf> (raw)
In-Reply-To: <20210803194758.GH27036@scaer>

Hello,

On Tue, 3 Aug 2021 21:47:58 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> People are really still using tarballs in these days? ;-) But OK, you've
> got a point.
> 
> However, I would still think that people who want to follow a process
> when updating are probably already using buildroot a git submodule of
> some sorts, so yes, they will have a git tree to look at.
> 
> People who use a released tarball are not really looking for a sustained
> or long-term vision, and are not planning on upgrading.

I was also surprised, but the other day, a person working for a large
IP vendor company complained that he was not able to download the
Buildroot tarballs. For some reason, the IP of this company had been
blocked in iptables rules of buildroot.org. When I suggested to use Git
instead, and especially the Github or Gitlab mirrors as a workaround,
it apparently wasn't considered really a good solution.

So it does seem like some people are still using the tarballs, indeed.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-08-04  1:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 16:22 [Buildroot] [RFC 1/2] docs/manual/migrating.txt: add section with general migrating tips Arnout Vandecappelle (Essensium/Mind)
2021-08-02 16:22 ` [Buildroot] [RFC 2/2] docs/manual/migrating.txt: add "individual packages" section Arnout Vandecappelle (Essensium/Mind)
2021-08-03  5:48   ` Yann E. MORIN
2021-08-03 15:19     ` Arnout Vandecappelle
2021-08-03 18:56       ` Michael Nosthoff via buildroot
2021-08-03 19:47         ` Yann E. MORIN
2021-08-03 21:35           ` Thomas Petazzoni [this message]
2021-08-02 20:55 ` [Buildroot] [RFC 1/2] docs/manual/migrating.txt: add section with general migrating tips Yann E. MORIN
2021-08-03 15:18   ` Arnout Vandecappelle

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=20210803233523.5e2b7ff6@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=buildroot@heine.tech \
    --cc=yann.morin.1998@free.fr \
    /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