From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] pkg-infra: introduce pre/post-step hooks
Date: Mon, 14 Oct 2013 09:16:09 +0200 [thread overview]
Message-ID: <20131014091609.06dcc63c@skate> (raw)
In-Reply-To: <f6240fcb39c5dcbfe7a74cc74da3089e3c982ae5.1381705600.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Mon, 14 Oct 2013 01:11:25 +0200, Yann E. MORIN wrote:
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> This hooks will let us instrument the build process in many ways:
> - log current step to see what broke
> - time each step to see what is worth optimising
> - sanity-check installed files (rpath, overwritten files...)
> - call user-provided script
> - ...
>
> The steps are fine-grain, and all have a 'start' and a 'end' hooks.
> Here is the list of available steps (19 total):
> - extract, post-extract
> - pre-patch, patch, post-patch
> - pre-configure, configure, post-configure
> - build, post-build
> - install-host, post-install-host
> - install-staging, post-install-staging, pkg-config-staging
> - install-image, post-install-image
> - install-target, post-install-target
>
> The download, clean, uninstall steps are not instrumented on purpose.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
I am not sure to follow why we're introducing additional hooks here.
Why don't we generalize the existing pre/post hooks mechanism to *all*
steps (by all I mean the steps you are interested in instrumenting),
and use that to hook the different things you introduce in patch 2, 3,
4 ?
Also, do we really need to have hook points for the pre-hooks and
post-hooks each time?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-14 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 23:11 [Buildroot] [pull request] [RFC] Pull request for branch yem/instrument-build Yann E. MORIN
2013-10-13 23:11 ` [Buildroot] [PATCH 1/4] pkg-infra: introduce pre/post-step hooks Yann E. MORIN
2013-10-14 7:16 ` Thomas Petazzoni [this message]
2013-10-14 16:50 ` Yann E. MORIN
2013-10-13 23:11 ` [Buildroot] [PATCH 2/4] pkg-infra: add hook to log timing of steps Yann E. MORIN
2013-10-13 23:11 ` [Buildroot] [PATCH 3/4] Makefile: export BUILD_DIR Yann E. MORIN
2013-10-14 10:54 ` Peter Korsgaard
2013-10-14 17:05 ` Yann E. MORIN
2013-10-13 23:11 ` [Buildroot] [PATCH 4/4] pkg-infra: add user-supplied step-hooks Yann E. MORIN
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=20131014091609.06dcc63c@skate \
--to=thomas.petazzoni@free-electrons.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.