From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: log current message
Date: Mon, 07 Oct 2013 22:53:34 +0200 [thread overview]
Message-ID: <2510480.hUTq69UsTb@sagittae> (raw)
In-Reply-To: <20131007165956.GE9561@free.fr>
On Monday 07 October 2013 18:59:56 Yann E. MORIN wrote:
[...]
> I have another interesting idea about such a script: detect whether a
> package overwrites or otherwise modifies a file already existing in
> staging/ and/or target/ to assess for the sanity of the packaging.
I wrote something like this. It is able to track owner of each files of
target/ and host/. It generates list of owners[1][2]. These list may be
usefull to generate binary packages.
I am also able to generate list of overwritten files[3][4].
Once I have list of owners in host/, I can track which files are
accessed during build and compute dependencies between packages[5].
As you notice, it is only a proof of concept. There is plenty of false
positives and I noticed many problems. Especially, current script is not
very reliable when I launch compilation from a dirty directory.
It is currently done by launching a daemon which watch target and host
(using inotify) during each step a built. This daemon log access to
files and another script post-process it. (I think, I would have far
better results if I maintain in real time a database of owners of all
installed files). I may send patches if you are interested (but they are
a little ugly).
[1] http://sysmic.org/~jezz/instrument/host_owners.gz
[2] http://sysmic.org/~jezz/instrument/target_owners.gz
[3] http://sysmic.org/~jezz/instrument/host_owners.err.gz
[4] http://sysmic.org/~jezz/instrument/target_owners.err.gz
[5] http://sysmic.org/~jezz/instrument/depends
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2013-10-07 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 11:19 [Buildroot] [PATCH] pkg-infra: log current message Yann E. MORIN
2013-10-06 14:31 ` Thomas Petazzoni
2013-10-07 10:09 ` Jérôme Pouiller
2013-10-07 12:07 ` Thomas Petazzoni
2013-10-07 16:48 ` Yann E. MORIN
2013-10-07 16:59 ` Yann E. MORIN
2013-10-07 17:19 ` Thomas Petazzoni
2013-10-08 16:47 ` Arnout Vandecappelle
2013-10-07 20:53 ` Jérôme Pouiller [this message]
2013-10-07 19:46 ` Jérôme Pouiller
2013-10-08 16:53 ` Arnout Vandecappelle
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=2510480.hUTq69UsTb@sagittae \
--to=jezz@sysmic.org \
--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.