From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
Asaf Kahlon <asafka7@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
buildroot@buildroot.org,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Vincent Fazio <vfazio@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-remi: fix pep517 build
Date: Thu, 9 May 2024 23:14:11 +0200 [thread overview]
Message-ID: <20240509231411.07a42954@windsurf> (raw)
In-Reply-To: <9e8a2daf-327b-4d22-88a6-fda7b38d4d78@mind.be>
On Thu, 9 May 2024 22:54:34 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> Theoretically I agree. However, IIUC, the dependencies that are checked are
> usually _runtime_ dependencies anyway, so we don't have it as an actual
> dependency.
Well, we do select them. But I guess you mean that since they are not
guaranteed to be around at build time, there is no way to have a proper
dependency check?
If that's the case, then how are all the other packages that don't do
--skip-dependency-check achieving a successful build?
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:[~2024-05-09 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 11:54 [Buildroot] [PATCH 1/1] package/python-remi: fix pep517 build Fabrice Fontaine
2024-04-07 19:33 ` Arnout Vandecappelle via buildroot
2024-04-07 19:58 ` Fabrice Fontaine
2024-05-09 16:46 ` Thomas Petazzoni via buildroot
2024-05-09 20:54 ` Arnout Vandecappelle via buildroot
2024-05-09 21:14 ` Thomas Petazzoni via buildroot [this message]
2024-05-09 21:28 ` James Hilliard
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=20240509231411.07a42954@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=asafka7@gmail.com \
--cc=fontaine.fabrice@gmail.com \
--cc=gwenhael.goavec-merou@trabucayre.com \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox