Re: [bitbake-devel] [PATCH] bitbake-setup: pass install-buildtools options from config and CLI
Alexander Kanavin <[email protected]> Tue, 16 Jun 2026 16:26:29 +0200
| Newsgroups | org.openembedded.lists.bitbake-devel |
|---|---|
| Message-ID | <CANNYZj_j7irKNRdeGDpF6mfKit_78ML5=XQJ3CeZckcM3924ZA@mail.gmail.com> |
On Tue, 16 Jun 2026 at 16:18, Jaipaul Cheernam via lists.openembedded.org <[email protected]> wrote: > Agreed on removing --sdk-name and I have sent Patch v2 for review in oe-core. > > For --no-check — I'm fine removing it and having the install-buildtools auto-detect, but we need to decide on the failure mode: if the checksum file can't be fetched > (404 or network error), should we: > > (a) warn and continue the install without verification, or > (b) hard fail and refuse to install? > > If (a), we're effectively auto---no-check on failure, which may silently skip validation on transient network issues. If (b), users with custom/local > URLs that don't host checksum files would have no way to install without us re-adding an override flag or having them to add checksum file. > > I checked the history why "--no-check” was added and it was part of bf902a810f98f55dd9e8cb9e6c6b0903f9902157 > > What's your preference? Please note my comment in this thread. If we use bitbake fetcher with checksum in a bitbake-setup config file, then the checksum would be enforced in a way that is secure against tampering or accidental replacement. Alex