From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/5] help2man-native: Add 1.36.4 (GPLv2) and 1.38.2 (GPLv3)
Date: Fri, 15 Jul 2011 15:53:20 -0700 [thread overview]
Message-ID: <4E20C4E0.2030908@mentor.com> (raw)
In-Reply-To: <1310770123.20015.1259.camel@rex>
On 07/15/2011 03:48 PM, Richard Purdie wrote:
> On Fri, 2011-07-15 at 15:03 -0700, Tom Rini wrote:
>> These are 'side ports' of current oe.dev versions. PR is kept in sync
>> but we drop out the target recipes in order to punt on potential perl
>> problems.
>>
>> Signed-off-by: Tom Rini <tom_rini@mentor.com>
>> ---
>> .../help2man/help2man-native_1.36.4.bb | 26 ++++++++++++++++++++
>> .../help2man/help2man-native_1.38.2.bb | 24 ++++++++++++++++++
>> 2 files changed, 50 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-devtools/help2man/help2man-native_1.36.4.bb
>> create mode 100644 meta/recipes-devtools/help2man/help2man-native_1.38.2.bb
>>
> [...]
>> diff --git a/meta/recipes-devtools/help2man/help2man-native_1.38.2.bb b/meta/recipes-devtools/help2man/help2man-native_1.38.2.bb
>> new file mode 100644
>> index 0000000..5612eda
>> --- /dev/null
>> +++ b/meta/recipes-devtools/help2man/help2man-native_1.38.2.bb
>> @@ -0,0 +1,24 @@
>> +DESCRIPTION = "Program to create simple man pages"
>> +SECTION = "devel"
>> +LICENSE = "GPLv3"
>> +LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
>> +DEPENDS = "autoconf-native automake-native"
>> +PR = "r2"
>> +
>> +SRC_URI = "${GNU_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz"
>> +SRC_URI[md5sum] = "426671c6fe79e5ef2233303367eab5a6"
>> +SRC_URI[sha256sum] = "952c29561bce8b233aa10af7f0e0c79c8243712810bf8ddf01e6efd82ce250d1"
>> +
>> +inherit autotools native
>> +
>> +EXTRA_OECONF = "--disable-nls"
>> +
>> +# We don't want to reconfigure things
>> +do_configure() {
>> + oe_runconf
>> +}
>
> At the very least I'd like to know why we can't do this. Its a great way
> to hide bugs (such as libtool rpath injection issues, admittedly in the
> target case).
In oe.dev, chicken and egg problem wrt perl. Here, I'll see if we can
drop this part too, as part of a v2 with the older help2man dropped and
per IRC, mercurial-native moved over to a meta-oe patch (but keeping the
sanity.bbclass/bitbake.conf change).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-07-15 22:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 22:03 [PATCH 0/5] Optionally trade required_utils for -native builds Tom Rini
2011-07-15 22:03 ` [PATCH 1/5] mercurial-native: Add 1.9 version Tom Rini
2011-07-15 22:14 ` Khem Raj
2011-07-15 22:22 ` Tom Rini
2011-07-15 22:03 ` [PATCH 2/5] bitbake.conf, sanity.bbclass: Make mercurial-native optional Tom Rini
2011-07-15 22:03 ` [PATCH 3/5] help2man-native: Add 1.36.4 (GPLv2) and 1.38.2 (GPLv3) Tom Rini
2011-07-15 22:24 ` Saul Wold
2011-07-15 22:29 ` Tom Rini
2011-07-15 22:41 ` Saul Wold
2011-07-15 22:47 ` Richard Purdie
2011-07-15 22:48 ` Richard Purdie
2011-07-15 22:53 ` Tom Rini [this message]
2011-07-18 22:13 ` Tom Rini
2011-07-19 12:17 ` Phil Blundell
2011-07-19 14:18 ` Tom Rini
2011-07-15 22:03 ` [PATCH 4/5] sanity.bbclass: Add help2man-native to ASSUME_PROVIDED if found Tom Rini
2011-07-15 22:03 ` [PATCH 5/5] autotools.bbclass: Add help2man-native to the main DEPENDS tree Tom Rini
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=4E20C4E0.2030908@mentor.com \
--to=tom_rini@mentor.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