From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] texinfo: fix info not work
Date: Wed, 24 Sep 2014 17:16:08 +0800 [thread overview]
Message-ID: <54228BD8.2060908@windriver.com> (raw)
In-Reply-To: <CAJTo0LZCcE0PysOXErBHaoyOU=izE88MkS5tLNB1q1ZGuijiiw@mail.gmail.com>
On 09/24/2014 04:40 AM, Burton, Ross wrote:
> On 23 September 2014 21:37, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> I think there are a few issues here. Firstly, this postinst can run at
>> build time which means there is a dependency on texinfo-native. I guess
>> if this fails, it will just run on target so its probably "harmless" but
>> not deterministic. Secondly, anything installing an info directory
>> really needs to update the dir files with its own postinst. For optimal
>> handling at rootfs time, that will need trigger/intercept support.
>>
>> So this probably can merge as it improves things however we need some
>> enhacement bugs opening related to this, we may want to force the
>> postinst to run on target for now so things are deterministic too.
> There's a texinfo.bbclass which all recipes installing info files are
> probably inheriting anyway, so moving the postinst there should solve
> the race on the directory. That class says that texinfo-native is
> assume-provided but you'll want to check that usual configurations
> ship install-info alongside makeinfo on the distributions we support.
Hi Ross,
I am afraid moving the postinst to texinfo.bbclass will cause some
potential issues:
- It will be invoked many times if multiple packages installed.
- We could not use a generic way to name pkg_postinst.
Such as texinfo recipe, we need pkg_postinst_info.
I will refer what Ubuntu/Debian did, add postinst/postrm to info
packages.
//Hongxu
> Ross
next prev parent reply other threads:[~2014-09-24 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:19 [PATCH 0/3] man/info: fix not support xz/bz2 compression Hongxu Jia
2014-09-23 14:19 ` [PATCH 1/3] busybox: enable CONFIG_BZIP2/CONFIG_XZ/CONFIG_UNXZ by default Hongxu Jia
2014-09-23 14:47 ` Burton, Ross
2014-09-24 10:46 ` Hongxu Jia
2014-09-23 14:19 ` [PATCH 2/3] man: fix not support xz/bz2 compression Hongxu Jia
2014-09-23 14:19 ` [PATCH 3/3] texinfo: fix info not work Hongxu Jia
2014-09-23 14:52 ` Burton, Ross
2014-09-23 20:37 ` Richard Purdie
2014-09-23 20:40 ` Burton, Ross
2014-09-24 9:16 ` Hongxu Jia [this message]
2014-09-24 10:50 ` Burton, Ross
2014-09-24 8:58 ` Hongxu Jia
2014-09-23 15:16 ` [PATCH 0/3] man/info: fix not support xz/bz2 compression Mark Hatle
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=54228BD8.2060908@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.com \
/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