From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Geoff Levand <geoff@infradead.org>,
Anisse Astier <anisse@astier.eu>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Marcin Niestroj <m.niestroj@grinn-global.com>,
Buildroot Mailing List <buildroot@buildroot.org>,
Romain Naour <romain.naour@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Thomas Perale <thomas.perale@mind.be>,
Thomas Perale <thomas.perale@essensium.com>
Subject: Re: [Buildroot] [PATCH 3/4] package/go-bin: new package
Date: Mon, 17 Oct 2022 20:42:32 +0200 [thread overview]
Message-ID: <20221017204232.652f8e89@windsurf> (raw)
In-Reply-To: <20221017180350.GC3666@scaer>
On Mon, 17 Oct 2022 20:03:50 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Agreed. The default should be to build everything from source when
> sources are available. The pre-built packages are only a fallback as
> a convenience for those that are too much in a hurry.
Except we do exactly the opposite for Rust, and I'm not sure for the
host compiler of those languages it is a good idea to cause such a
major impact on the default build time faced by our users. I clearly
understand the need to be able from source and appreciate how important
it is, but I'm not so sure the default should be to build all those
compilers from source.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-17 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221017142849.41399-1-thomas.perale@mind.be>
[not found] ` <20221017142849.41399-4-thomas.perale@mind.be>
2022-10-17 16:05 ` [Buildroot] [PATCH 3/4] package/go-bin: new package Christian Stewart via buildroot
2022-10-17 18:03 ` Yann E. MORIN
2022-10-17 18:42 ` Thomas Petazzoni via buildroot [this message]
2022-10-17 18:52 ` Christian Stewart via buildroot
[not found] ` <20221017142849.41399-2-thomas.perale@mind.be>
2022-10-17 16:06 ` [Buildroot] [PATCH 1/4] package/goc: new virtual package Christian Stewart via buildroot
2022-10-17 17:55 ` Yann E. MORIN
2022-10-17 18:10 ` Christian Stewart via buildroot
2022-10-17 18:30 ` Thomas Perale via buildroot
2022-10-17 18:44 ` Yann E. MORIN
2022-10-17 18:51 ` Christian Stewart via buildroot
2022-10-18 8:03 ` Thomas Perale via buildroot
2022-10-17 18:48 ` Thomas Petazzoni via buildroot
[not found] <20221017143125.41622-1-thomas.perale@mind.be>
[not found] ` <20221017143125.41622-4-thomas.perale@mind.be>
2022-10-17 16:13 ` [Buildroot] [PATCH 3/4] package/go-bin: new package Christian Stewart via buildroot
2022-10-18 6:36 ` Thomas Petazzoni via buildroot
2022-10-17 15:17 [Buildroot] [PATCH 0/4] Add support for using a pre-compiled Go compiler Thomas Perale via buildroot
2022-10-17 15:17 ` [Buildroot] [PATCH 3/4] package/go-bin: new package Thomas Perale via buildroot
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=20221017204232.652f8e89@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=anisse@astier.eu \
--cc=festevam@gmail.com \
--cc=geoff@infradead.org \
--cc=m.niestroj@grinn-global.com \
--cc=romain.naour@gmail.com \
--cc=thomas.perale@essensium.com \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
--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