On 2011?11?07? 19:36, Koen Kooi wrote:
Op 7 nov. 2011, om 12:13 heeft Xiaofeng Yan het volgende geschreven:

From: Xiaofeng Yan<xiaofeng....@windriver.com>

libarchive: update to 2.8.5

Signed-off-by: Xiaofeng Yan<xiaofeng....@windriver.com>
---
...rchive_2.8.4.yocto.1.bb =>  libarchive_2.8.5.bb} |    8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-extended/libarchive/{libarchive_2.8.4.yocto.1.bb =>  
libarchive_2.8.5.bb} (76%)

diff --git a/meta/recipes-extended/libarchive/libarchive_2.8.4.yocto.1.bb 
b/meta/recipes-extended/libarchive/libarchive_2.8.5.bb
similarity index 76%
rename from meta/recipes-extended/libarchive/libarchive_2.8.4.yocto.1.bb
rename to meta/recipes-extended/libarchive/libarchive_2.8.5.bb
index 94d261b..1bc49e2 100644
--- a/meta/recipes-extended/libarchive/libarchive_2.8.4.yocto.1.bb
+++ b/meta/recipes-extended/libarchive/libarchive_2.8.5.bb
@@ -9,19 +9,19 @@ DEPENDS = "libxml2"

# We need to repack the tarball due undistributable content on the upstream one.
# More details at http://code.google.com/p/libarchive/issues/detail?id=162
-SRC_URI = "http://autobuilder.yoctoproject.org/sources/libarchive-${PV}.tar.gz 
\
+SRC_URI = "http://libarchive.googlecode.com/files/libarchive-${PV}.tar.gz \
            file://0001-Patch-from-upstream-revision-1990.patch \
            file://0002-Patch-from-upstream-revision-1991.patch \
-           file://0003-Patch-from-upstream-rev-2516.patch \
Why was only that patch removed? The commit message doesn't mention anything 
about it.

I have added description about the reason why removing this patch. Thanks for your review.
regards,
Yan
regards,

Koen



_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to