From: Saul Wold <saul.wold@intel.com>
To: Kang Kai <kai.kang@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/3] groff: update to 1.20.1
Date: Wed, 27 Apr 2011 15:47:10 -0700 [thread overview]
Message-ID: <4DB89CEE.8050702@intel.com> (raw)
In-Reply-To: <8924c9d60a2f03478c9b18ba54bad461d91553b8.1303895739.git.kai.kang@windriver.com>
On 04/27/2011 02:30 AM, Kang Kai wrote:
> From: Kang Kai<kai.kang@windriver.com>
>
> Update groff to 1.20.1, add SUMMARY and LICENSE info
>> From OE 70bf94cd8669f549ca90581e9592d409b6e24e2e
> Fixes [Yocto 879]
>
Why did you not updated the existing recipe, via a git mv and then edit
it. We do not keep older recipes around, so they should be cleaned up.
Also, why do we need a native for this recipe? For dealing with
documentation native side?
Sau!
> Signed-off-by: Kang Kai<kai.kang@windriver.com>
> ---
> meta/recipes-extended/groff/groff_1.20.1.bb | 36 +++++++++++++++++++++++++++
> 1 files changed, 36 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-extended/groff/groff_1.20.1.bb
>
> diff --git a/meta/recipes-extended/groff/groff_1.20.1.bb b/meta/recipes-extended/groff/groff_1.20.1.bb
> new file mode 100644
> index 0000000..e0e198f
> --- /dev/null
> +++ b/meta/recipes-extended/groff/groff_1.20.1.bb
> @@ -0,0 +1,36 @@
> +SUMMARY = "GNU Troff software"
> +DESCRIPTION = "The groff (GNU troff) software is a typesetting package which reads plain text mixed with \
> +formatting commands and produces formatted output."
> +SECTION = "base"
> +HOMEPAGE = "ftp://ftp.gnu.org/gnu/groff/"
> +LICENSE = "GPLv2"
> +PR = "r0"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
> +
> +SRC_URI = "${GNU_MIRROR}/groff/groff-${PV}.tar.gz"
> +
> +SRC_URI[md5sum] = "48fa768dd6fdeb7968041dd5ae8e2b02"
> +SRC_URI[sha256sum] = "b645878135cb620c6c417c5601bfe96172245af12045540d7344938b4c2cd805"
> +
> +DEPENDS = "groff-native"
> +DEPENDS_virtclass-native = ""
> +
> +inherit autotools
> +
> +PARALLEL_MAKE = ""
> +
> +do_configure_prepend() {
> + if [ "${BUILD_SYS}" != "${HOST_SYS}" ]; then
> + sed -i \
> + -e '/^GROFFBIN=/s:=.*:=${STAGING_BINDIR_NATIVE}/groff:' \
> + -e '/^TROFFBIN=/s:=.*:=${STAGING_BINDIR_NATIVE}/troff:' \
> + -e '/^GROFF_BIN_PATH=/s:=.*:=${STAGING_BINDIR_NATIVE}:' \
> + -e '/^GROFF_BIN_DIR=/s:=.*:=${STAGING_BINDIR_NATIVE}:' \
> + ${S}/contrib/*/Makefile.sub \
> + ${S}/doc/Makefile.in \
> + ${S}/doc/Makefile.sub
> + fi
> +}
> +
> +BBCLASSEXTEND = "native"
next prev parent reply other threads:[~2011-04-27 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 9:30 [PATCH 0/3] Fixes for LSB command check Kang Kai
2011-04-27 9:30 ` [PATCH 1/3] groff: update to 1.20.1 Kang Kai
2011-04-27 22:47 ` Saul Wold [this message]
2011-04-27 9:30 ` [PATCH 2/3] lsbsetup: add commands install_initd and remove_initd Kang Kai
2011-04-27 17:04 ` Saul Wold
2011-04-27 9:30 ` [PATCH 3/3] task-core-lsb: add xdg-utils into lsb image Kang Kai
-- strict thread matches above, loose matches on Subject: below --
2011-04-28 3:15 [PATCH 0/3] Fixes for LSB command check Kang Kai
2011-04-28 3:15 ` [PATCH 1/3] groff: update to 1.20.1 Kang Kai
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=4DB89CEE.8050702@intel.com \
--to=saul.wold@intel.com \
--cc=kai.kang@windriver.com \
--cc=poky@yoctoproject.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.