From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Buildhistory, was Re: [OE-core] do rootfs does not create log files
Date: Thu, 01 Mar 2012 14:31:11 +0000 [thread overview]
Message-ID: <13179298.lVtZb3KUcf@helios> (raw)
In-Reply-To: <CALbNGRQBCeQj=0dHAwAddM5cvJZhKLzyk8J5+WLAh7QFQBx_rg@mail.gmail.com>
On Thursday 01 March 2012 13:38:04 Andreas Müller wrote:
> Would it be big effort to have the package scripts (pre-/postinst,
> postrm) handled by buildhistory?
Do you mean you would like the contents of the scripts recorded in
buildhistory? If so, I guess this is possible; if we just output each script
to a separate file I don't think it should be too difficult. Making it work
nicely if you switch back to the old (symlinked) mode would be an extra trick,
though I'm starting to wonder if that's worth continuing to support.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-01 14:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 22:16 do rootfs does not create log files Andreas Müller
2012-02-05 23:24 ` Khem Raj
2012-02-05 23:24 ` [OE-core] " Khem Raj
2012-02-05 23:47 ` Andreas Müller
2012-02-05 23:58 ` Khem Raj
2012-02-06 7:46 ` Buildhistory, was " Koen Kooi
2012-02-06 7:46 ` Buildhistory, was Re: [OE-core] " Koen Kooi
2012-02-06 9:04 ` [oe] Buildhistory, was " Andreas Müller
2012-02-06 9:04 ` Buildhistory, was Re: [OE-core] " Andreas Müller
2012-02-06 9:06 ` [oe] Buildhistory, was " Andreas Müller
2012-02-06 9:06 ` [OE-core] " Andreas Müller
2012-02-06 9:09 ` [oe] " Koen Kooi
2012-02-06 9:09 ` [OE-core] " Koen Kooi
2012-02-06 9:28 ` [oe] " Richard Purdie
2012-02-06 9:28 ` [OE-core] " Richard Purdie
2012-03-01 12:38 ` Buildhistory, was Re: [OE-core] " Andreas Müller
2012-03-01 14:31 ` Paul Eggleton [this message]
2012-03-01 14:38 ` [oe] Buildhistory, was " Andreas Müller
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=13179298.lVtZb3KUcf@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.