From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] texinfo: fix info not work
Date: Tue, 23 Sep 2014 21:37:21 +0100 [thread overview]
Message-ID: <1411504641.4189.2.camel@ted> (raw)
In-Reply-To: <e33476eb2f61c8a8be679e15114ef90321239dde.1411473883.git.hongxu.jia@windriver.com>
On Tue, 2014-09-23 at 22:19 +0800, Hongxu Jia wrote:
> In texinfo, we didn't have info/dir entries, which caused
> info not work.
> ...
> root@qemux86:~# info info
> info: dir: No such file or directory
> ...
> Invoke install-info to create info/dir entries in pkg_postinst_info.
>
> Also fix a QA Issue
> ...
> ERROR: QA Issue: texinfo: Files/directories were installed but not shipped
> /usr/share/info/info.info.bz2
> /usr/share/info/info-stnd.info.bz2 [installed-vs-shipped]
> ...
>
> [YOCTO #6751]
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> meta/recipes-extended/texinfo/texinfo_5.2.bb | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-extended/texinfo/texinfo_5.2.bb b/meta/recipes-extended/texinfo/texinfo_5.2.bb
> index be90aba..91552a9 100644
> --- a/meta/recipes-extended/texinfo/texinfo_5.2.bb
> +++ b/meta/recipes-extended/texinfo/texinfo_5.2.bb
> @@ -51,7 +51,7 @@ do_install_append_class-native() {
> PACKAGES += "info info-doc"
>
> FILES_info = "${bindir}/info ${bindir}/infokey ${bindir}/install-info"
> -FILES_info-doc = "${infodir}/info.info ${infodir}/dir ${infodir}/info-*.info \
> +FILES_info-doc = "${infodir}/info.info* ${infodir}/dir ${infodir}/info-*.info* \
> ${mandir}/man1/info.1* ${mandir}/man5/info.5* \
> ${mandir}/man1/infokey.1* ${mandir}/man1/install-info.1*"
>
> @@ -61,4 +61,10 @@ FILES_${PN}-doc = "${infodir}/texinfo* \
> ${datadir}/${tex_texinfo} \
> ${mandir}/man1 ${mandir}/man5"
>
> +pkg_postinst_info () {
> + for f in `find $D/${infodir} -name "*.info*"`; do
> + install-info $f $D/${infodir}/dir
> + done
> +}
> +
> BBCLASSEXTEND = "native"
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.
Cheers,
Richard
next prev parent reply other threads:[~2014-09-23 20:37 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 [this message]
2014-09-23 20:40 ` Burton, Ross
2014-09-24 9:16 ` Hongxu Jia
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=1411504641.4189.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox