From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [Dizzy backport] [meta-oe][PATCH] xmlto: remove recipe as it's in OE core
Date: Thu, 22 Jan 2015 09:42:25 -0800 [thread overview]
Message-ID: <54C13681.1090905@gmail.com> (raw)
In-Reply-To: <54BF7E14.3080401@digi.com>
will do.
- armin
On 01/21/2015 02:23 AM, Javier Viguera wrote:
> Hi all,
>
> Poky/OE-core added xmlto for Dizzy, but in meta-oe it has only been
> removed in master so for Dizzy the recipe is duplicated:
>
> $ bitbake-layers show-overlayed
> xmlto:
> meta-oe 0.0.25
> meta 0.0.25
>
> Could this removal patch be backported?
>
> -
> Regards,
>
> Javier Viguera
>
>
> On 28/11/14 10:13, Chen Qi wrote:
>> Remove xmlto recipe from meta-oe because it's in OE core now.
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>> .../xmlto-0.0.25/obsolete_automake_macros.patch | 12 ------------
>> meta-oe/recipes-support/xmlto/xmlto_0.0.25.bb | 18
>> ------------------
>> 2 files changed, 30 deletions(-)
>> delete mode 100644
>> meta-oe/recipes-support/xmlto/xmlto-0.0.25/obsolete_automake_macros.patch
>> delete mode 100644 meta-oe/recipes-support/xmlto/xmlto_0.0.25.bb
>>
>> diff --git
>> a/meta-oe/recipes-support/xmlto/xmlto-0.0.25/obsolete_automake_macros.patch
>> b/meta-oe/recipes-support/xmlto/xmlto-0.0.25/obsolete_automake_macros.patch
>>
>> deleted file mode 100644
>> index faa8acc..0000000
>> ---
>> a/meta-oe/recipes-support/xmlto/xmlto-0.0.25/obsolete_automake_macros.patch
>>
>> +++ /dev/null
>> @@ -1,12 +0,0 @@
>> -diff -Nurd xmlto-0.0.25/configure.in xmlto-0.0.25/configure.in
>> ---- xmlto-0.0.25/configure.in 2011-12-01 17:49:00.000000000 +0200
>> -+++ xmlto-0.0.25/configure.in 2013-01-07 05:24:16.169953519 +0200
>> -@@ -1,7 +1,7 @@
>> - AC_INIT(xmlto, 0.0.25)
>> - AC_CONFIG_SRCDIR(xmlto.spec.in)
>> - AM_INIT_AUTOMAKE([dist-bzip2 subdir-objects 1.6])
>> --AM_CONFIG_HEADER(config.h)
>> -+AC_CONFIG_HEADERS(config.h)
>> -
>> - AC_PROG_CC
>> - AM_PROG_CC_C_O
>> diff --git a/meta-oe/recipes-support/xmlto/xmlto_0.0.25.bb
>> b/meta-oe/recipes-support/xmlto/xmlto_0.0.25.bb
>> deleted file mode 100644
>> index 9188c8a..0000000
>> --- a/meta-oe/recipes-support/xmlto/xmlto_0.0.25.bb
>> +++ /dev/null
>> @@ -1,18 +0,0 @@
>> -SUMMARY = "A shell-script tool for converting XML files to various
>> formats"
>> -HOMEPAGE = "https://fedorahosted.org/xmlto/"
>> -SECTION = "docs/xmlto"
>> -LICENSE = "GPLv2"
>> -
>> -LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"
>> -
>> -PR = "r1"
>> -
>> -SRC_URI =
>> "https://fedorahosted.org/releases/x/m/xmlto/xmlto-${PV}.tar.gz \
>> - file://obsolete_automake_macros.patch \
>> -"
>> -SRC_URI[md5sum] = "a88cd3f08789b4825d1ac89fa065170d"
>> -SRC_URI[sha256sum] =
>> "c52b56d929e8d20fc19cd3b7ec238f8d039730c56ee311cc352e843147e3e31a"
>> -
>> -inherit autotools
>> -
>> -BBCLASSEXTEND = "native nativesdk"
>>
>
>
prev parent reply other threads:[~2015-01-22 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 9:13 [meta-oe][PATCH] xmlto: remove recipe as it's in OE core Chen Qi
2015-01-21 10:23 ` [Dizzy backport] " Javier Viguera
2015-01-22 17:42 ` akuster808 [this message]
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=54C13681.1090905@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@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