From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/11] support/scripts/pkg-stats: store dependencies of package
Date: Sat, 4 Jan 2020 10:39:36 +0100 [thread overview]
Message-ID: <20200104103936.06a7a228@windsurf> (raw)
In-Reply-To: <CAEyMn7YhmtuRSfZscUqyNm7wEWcye5x9YZO=5T8VPPzbEBuErQ@mail.gmail.com>
On Fri, 3 Jan 2020 17:39:13 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> Thought it is a good idea because I saw that on the
> https://layers.openembedded.org/layerindex/recipe/45257/. They also
> show the dependencies with a note that this can differ dependent on
> the real used configuration. But if you think it is too confusing I
> can drop that.
Don't get me wrong, it would be nice to have the dependencies of
packages, but it is simply not possible.
Consider a package like this:
FOO_DEPENDENCIES = bar baz
ifeq ($(BR2_PACKAGE_LIBPNG),y)
FOO_DEPENDENCIES += libpng
endif
If you run "make VARS=FOO_DEPENDENCIES printvars" with no Buildroot
configuration defined, or with a Buildroot configuration defined that
has the libpng package disabled, it will return:
FOO_DEPENDENCIES=bar baz
If however, you run the same command with a Buildroot configuration
defined that has the libpng package enabled, it will return:
FOO_DEPENDENCIES=bar baz libpng
So as you can see, there is nothing like "the list of all dependencies
of a package" that you can get with printvars. Lots of dependencies are
optional. Some are even conflicting, like a package can depend on A
*or* B, but not both. Etc.
This is why I think it is not a good idea to show those dependencies,
because they simply cannot be correct "in general": they can only be
correct within the context of a particular Buildroot configuration.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-04 9:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 15:18 [Buildroot] [PATCH 00/11] pkg-stats json output improvements Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 01/11] support/scripts/pkg-stats: store latest version in a hash Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 02/11] support/scripts/pkg-stats: store pkg dir path Heiko Thiery
2020-01-03 15:21 ` Thomas Petazzoni
2020-01-03 18:40 ` Avraham Shukron
2020-01-03 15:18 ` [Buildroot] [PATCH 03/11] support/scripts/pkg-stats: store patch info in a hash Heiko Thiery
2020-01-03 15:23 ` Thomas Petazzoni
2020-01-03 16:23 ` Heiko Thiery
2020-01-03 16:26 ` Thomas Petazzoni
2020-01-03 16:31 ` Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 04/11] support/scripts/pkg-stats: do not exclued pkg name in json output Heiko Thiery
2020-01-03 15:24 ` Thomas Petazzoni
2020-01-03 16:29 ` Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 05/11] support/scripts/pkg-stats: parse and set developers info Heiko Thiery
2020-01-03 15:26 ` Thomas Petazzoni
2020-01-03 16:32 ` Heiko Thiery
2020-01-03 16:39 ` Thomas Petazzoni
2020-01-05 19:18 ` Arnout Vandecappelle
2020-01-05 21:49 ` Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 06/11] support/scripts/pkg-stats: store licences of package Heiko Thiery
2020-01-03 15:28 ` Thomas Petazzoni
2020-01-03 16:36 ` Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 07/11] support/scripts/pkg-stats: store dependencies " Heiko Thiery
2020-01-03 15:29 ` Thomas Petazzoni
2020-01-03 16:39 ` Heiko Thiery
2020-01-04 9:39 ` Thomas Petazzoni [this message]
2020-01-04 12:28 ` Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 08/11] support/scripts/pkg-stats: add generic package status field Heiko Thiery
2020-01-03 15:34 ` Thomas Petazzoni
2020-01-03 16:52 ` Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 09/11] support/scripts/pkg-stats; use url status from dict for check Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 10/11] support/scripts/pkg-stats: add package count to stats Heiko Thiery
2020-01-03 15:35 ` Thomas Petazzoni
2020-01-03 16:43 ` Heiko Thiery
2020-01-03 15:18 ` [Buildroot] [PATCH 11/11] support/scripts/pkg-stats: create and store defconfig information Heiko Thiery
2020-01-03 15:38 ` Thomas Petazzoni
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=20200104103936.06a7a228@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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