From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/8] core/show-info: report the ordered list of build steps
Date: Sat, 11 Apr 2020 20:20:17 +0200 [thread overview]
Message-ID: <20200411182017.GQ29898@scaer> (raw)
In-Reply-To: <CAB4xu_15BFXQ3VFnrp8j5b8ivr=pGN2HN5UarW8dz-R+XRk5Dw@mail.gmail.com>
Philippe, All,
On 2020-04-11 11:06 -0400, Philippe Proulx spake thusly:
> On Sat, Apr 11, 2020 at 10:19 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
[--SNIP--]
> If you tell me that things such build step order and stamp file names do
> not change for many years and as such can be considered as interfaces,
> I'm fine with this.
They are not an interface, definitely not (IMHO). But they are stable
enough that you can build something on them and not expect a breakage
that often.
But an interface? No, we can't commit to that.
> It's always a balance between adding the same logic to all the viewers
> and generating less data.
Since the output of show-info is for machine consumption, and is not
geared at human consuption without first being processed, I don;t see a
problem with generating "more" data.
> My tool could be part of the Buildroot project, but I doubt you'll want
> something that depends on PyQt5 in there.
Not a problem, as it is not a mandatory tool. We already have
utils/brmake that uses unbuffer, which is not available on most distros
by default.
> However, I could certainly
> contribute a Python module which offers utilities over the `show-info`
> output so as to have a versioned, object-oriented API, and then import
> it from an external tool. This way, even if `show-info` changes, the
> Python module can continue to offer the same (non-breaking) interface.
You can't guarantee that either: some keys may disapear, so such a
module could not expose them any more either, so not a stable API.
All you could provide as a stable API, is a way to rerieve basic
information, like the list of packages and such. Or a way to query
keys, which would not provide much more than what 'import json' would.
Regards,
Yann E. MORIN.
> I still think we somewhat need the `build_dir` entry though.
>
> Phil
>
> >
> > Best regards,
> >
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-04-11 18:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 8:12 [Buildroot] [PATCH 0/8] core/show-info: export extra information about the package build (branch yem/show-info-extras) Yann E. MORIN
2020-04-11 8:12 ` [Buildroot] [PATCH 1/8] core/show-info: do not show install types for host packages Yann E. MORIN
2020-04-25 12:57 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 2/8] infra/pkg-generic: don't set INSTALL_{TARGET, STAGING, IMAGES} for host Yann E. MORIN
2020-04-25 12:57 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 3/8] core/show-info: report install types for virtual packages too Yann E. MORIN
2020-04-11 8:41 ` Thomas Petazzoni
2020-04-11 9:49 ` Yann E. MORIN
2020-04-25 13:07 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 4/8] core/show-info: report the package build directory Yann E. MORIN
2020-04-25 13:08 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 5/8] core/show-info: report whether a package is overriden Yann E. MORIN
2020-04-11 8:36 ` Thomas Petazzoni
2020-04-11 9:44 ` Yann E. MORIN
2020-04-11 12:42 ` Thomas Petazzoni
2020-04-11 13:22 ` Yann E. MORIN
2020-04-11 14:14 ` Thomas Petazzoni
2020-04-11 17:41 ` Yann E. MORIN
2020-04-11 8:12 ` [Buildroot] [PATCH 6/8] core/show-info: report package stamp files Yann E. MORIN
2020-04-11 8:38 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 7/8] core/show-info: report the ordered list of build steps Yann E. MORIN
2020-04-11 8:39 ` Thomas Petazzoni
2020-04-11 13:41 ` Philippe Proulx
2020-04-11 14:19 ` Thomas Petazzoni
2020-04-11 15:06 ` Philippe Proulx
2020-04-11 15:27 ` Thomas Petazzoni
2020-04-11 18:20 ` Yann E. MORIN [this message]
2020-04-11 18:12 ` Yann E. MORIN
2020-04-11 18:02 ` Yann E. MORIN
2020-04-11 8:12 ` [Buildroot] [PATCH 8/8] core/show-info: report image name of filesystems Yann E. MORIN
2020-04-25 13:12 ` Thomas Petazzoni
2020-04-25 13:32 ` Yann E. MORIN
2021-07-27 20:08 ` Arnout Vandecappelle
2020-04-25 13:13 ` [Buildroot] [PATCH 0/8] core/show-info: export extra information about the package build (branch yem/show-info-extras) 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=20200411182017.GQ29898@scaer \
--to=yann.morin.1998@free.fr \
--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