All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/8] core/show-info: report the ordered list of build steps
Date: Sat, 11 Apr 2020 17:27:26 +0200	[thread overview]
Message-ID: <20200411172726.555e75b8@windsurf.home> (raw)
In-Reply-To: <CAB4xu_15BFXQ3VFnrp8j5b8ivr=pGN2HN5UarW8dz-R+XRk5Dw@mail.gmail.com>

Hello,

On Sat, 11 Apr 2020 11:06:05 -0400
Philippe Proulx <eeppeliteloop@gmail.com> wrote:

> > However, I still don't understand why your tool is not capable of
> > having this knowledge about the stamp files. This is something that
> > rarely changes. I think we haven't changed the stamp files since... 5
> > years? More? If your tool is in the Buildroot tree itself, it can
> > simply be updated if there is ever a change in the sequencing of steps.  
> 
> Yes of course.
> 
> I was only trying to improve Yann's solution considering your comments
> about data redundancy.

Sure, and your proposal makes sense if we believe we need to have this
build sequencing information exposed in the JSON output.

> 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.

I don't think we can really consider these as stable interfaces, but it
is sufficiently stable to rely on it.

> It's always a balance between adding the same logic to all the viewers
> and generating less data.
> 
> My tool could be part of the Buildroot project, but I doubt you'll want
> something that depends on PyQt5 in there.

I don't see why we couldn't have it in the tree. It's not a mandatory
tool, so it's fine to have something that depends on PyQt5.

> 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.
> 
> I still think we somewhat need the `build_dir` entry though.

Yes, for the build_dir entry, I definitely agree, it is useful and
needed.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-04-11 15:27 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 [this message]
2020-04-11 18:20           ` Yann E. MORIN
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=20200411172726.555e75b8@windsurf.home \
    --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 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.