From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: rs@ti.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
alex.kanavin@gmail.com, bitbake-devel@lists.openembedded.org,
denis@denix.org, reatmon@ti.com
Subject: Re: [bitbake-devel] [PATCH v2] bitbake-worker: remove the network flag
Date: Sun, 10 Sep 2023 23:16:39 +0200 [thread overview]
Message-ID: <20230910211639f1b8e744@mail.local> (raw)
In-Reply-To: <ede700bf-05f0-4e23-b173-ba2df6de2603@ti.com>
On 10/09/2023 15:50:22-0500, Randolph Sapp via lists.openembedded.org wrote:
> Thanks for the background. I won't push this issue anymore. The current
> method does seem to be pretty good at passively catching offending tasks.
>
This is certainly way more important for your customers than you
realize. The proxy issue is not actually an issue because it is very
likely that anyway they would have to set up a local mirror to ensure
they are able to rebuild without relying on a third party. You should
rather teach them to do that instead of working around the networking
issues they are creating for themselves.
This is even more important as the companies having those network issue
are probably the one that care the most about the correctness of spdx.
Really, the proper fix is in the fetcher.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-09-10 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 19:46 [PATCH v2] bitbake-worker: remove the network flag rs
2023-09-10 19:57 ` Alexander Kanavin
2023-09-10 20:11 ` [EXTERNAL] " Randolph Sapp
2023-09-10 20:16 ` Alexander Kanavin
2023-09-10 20:17 ` Richard Purdie
2023-09-10 20:50 ` [EXTERNAL] " Randolph Sapp
2023-09-10 21:16 ` Alexandre Belloni [this message]
2023-09-10 21:45 ` [EXTERNAL] Re: [bitbake-devel] " Randolph Sapp
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=20230910211639f1b8e744@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=denis@denix.org \
--cc=reatmon@ti.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rs@ti.com \
/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.