From: edwin.zhai@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Fix hard path in opensp
Date: Tue, 13 Sep 2011 21:43:30 +0800 [thread overview]
Message-ID: <cover.1315920902.git.edwin.zhai@intel.com> (raw)
From: Zhai Edwin <edwin.zhai@intel.com>
Saul,
This is the new version to fix the hard path in opensp. After 2nd thought, I'm
reluctant to change the search directory path handling code in nsgmls in case
of any likely side effect to other package. I change the iputils' makefile to
avoid "../" in the sysid path, and it really works without regression.
This is reasonable, as other package, like linuxdoc-tools-native, make a lot of
works before calling nsgmls: prepare search directory path with "-D", introduce
a huge perf module to handle the sgml2XXX conversion...
Pls. help to review.
Thanks,
Edwin
The following changes since commit 52835dd30110d51a839872f198eef3b12e369850:
avahi: only use gtk if DISTRO_FEATURES includes x11 (2011-09-07 23:44:29 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib gzhai/master2
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=gzhai/master2
Zhai Edwin (1):
opensp: Fix hard path in native nsgmls.
meta/recipes-devtools/opensp/opensp_1.5.bb | 4 +-
.../iputils/files/nsgmls-path-fix.patch | 27 ++++++++++++++++++++
meta/recipes-extended/iputils/iputils_s20101006.bb | 1 +
3 files changed, 30 insertions(+), 2 deletions(-)
create mode 100644 meta/recipes-extended/iputils/files/nsgmls-path-fix.patch
next reply other threads:[~2011-09-13 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 13:43 edwin.zhai [this message]
2011-09-13 13:43 ` [PATCH 1/1] opensp: Fix hard path in native nsgmls edwin.zhai
2011-09-13 16:09 ` Richard Purdie
2011-09-13 15:48 ` [PATCH 0/1] Fix hard path in opensp Saul Wold
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=cover.1315920902.git.edwin.zhai@intel.com \
--to=edwin.zhai@intel.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