Skip to contentSkip to conversation

giflib: Move to OE-Core

PATCH In review Samuel Stirtzel 2 participants 3 messages Mar 22, 2012

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 giflib: Move to OE-Core

* Allow Poky users to test and use meta-kde.
* Allow Users with an use case that excludes meta-oe to test and use meta-kde.

---
 meta-oe/recipes-devtools/giflib/giflib_4.1.6.bb |   20 --------------------
 1 files changed, 0 insertions(+), 20 deletions(-)
 delete mode 100644 meta-oe/recipes-devtools/giflib/giflib_4.1.6.bb
meta-oe/recipes-devtools/giflib/giflib_4.1.6.bb deleted +0 -20
deleted file mode 100644
index bd7b495..0000000
@@ -1,20 +0,0 @@
-DESCRIPTION = "shared library for GIF images"
-SECTION = "libs"
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://COPYING;md5=ae11c61b04b2917be39b11f78d71519a"
-PR = "r2"
-
-SRC_URI = "${SOURCEFORGE_MIRROR}/giflib/${BP}.tar.bz2"
-
-inherit autotools
-
-DEPENDS = "libsm"
-
-PACKAGES += "${PN}-utils"
-FILES_${PN} = "${libdir}/libgif.so.*"
-FILES_${PN}-utils = "${bindir}"
-
-BBCLASSEXTEND = "native"
-
-SRC_URI[md5sum] = "7125644155ae6ad33dbc9fc15a14735f"
-SRC_URI[sha256sum] = "e1c1ced9c5bc8f93ef0faf0a8c7717abf784d10a7b270d2285e8e1f3b93f2bed"
Signature · 1 line
1.7.5.4
#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 22-03-12 13:40, Samuel Stirtzel schreef:

Quoted 2 lines

* Allow Users with an use case that excludes meta-oe to test and use meta-kde.

What's that usecase? As other people said in a different thread: please explain. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJPayOBAAoJEHZqAkdh1vT6nLgP/3yrPJGfjPfDjPN3YNQ8EVDJ p87Vx1lFzs2zwdxU3PsOVI9jTANCSye386YsQxlQUQbw4EmNAXWck0eYSEbRvlK4 8M6+o+O2g1wUoBu+z0WH+GZxkHDkKXbUgE5bEjImyDJVSdxQgIuYZipo2LGQ7E4G zJg+1GaYd8wA6VnxiK2Q/pwKCWjiW2D1NrAouVfNN2cyawVdMkh8NsgaHyGDmgVh 9hsKxquaXAWKkqj8T/NIPUXvOCbKlFlTTl5Aqmj4KEM4Y5bPlMuOmkp6oFApaGWn k2f6c6GO8tSzdXVfMjus7jLeXIz1qIU+4YPi8N/vErnk05miFKo6rCXUFJV3BVDs Hbpnir9ufWl2H0Q3SG0otxqtj5Mwg9j7fB7iVQOudbYDlW8PGKfV01c9KYyLrgtY 9wFy1204AS+MsoGaWMA12dmhZeBaypm0FND85gVs0AsTRBrEsi7zVdhauOXpGZcg GHoUV+LIoWSHBjsaU+97aflH2+8la+zyDNVdzpBmik3sxlT9Xh8KffJOOHhkyy90 NQKeZ3lB+52GdXCh31MrAJz2huPESFAcLa+18mU+i8rxeYZYLh9/9QQMJmZyZFBT myP8Oj/2EGWRMCpH+D2NMxEZWKvqLuXjffLirr6pF3jwI6xMsCQzq7OmR+1pR2DL ijrM+EtzEDEOeog+HTbC
=LzmU
-----END PGP SIGNATURE-----

#2 lore raw

2012/3/22 Koen Kooi <[email protected]>:

Quoted 9 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 22-03-12 13:40, Samuel Stirtzel schreef:

Quoted 2 lines

* Allow Users with an use case that excludes meta-oe to test and use meta-kde.

What's that usecase? As other people said in a different thread: please explain.

The first comment is a direct explicit target group / use case. Then second comment is about a generic use case.
So it is rather making meta-kde more independent of meta-oe than any specific development setup.

Quoted 24 lines

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJPayOBAAoJEHZqAkdh1vT6nLgP/3yrPJGfjPfDjPN3YNQ8EVDJ p87Vx1lFzs2zwdxU3PsOVI9jTANCSye386YsQxlQUQbw4EmNAXWck0eYSEbRvlK4 8M6+o+O2g1wUoBu+z0WH+GZxkHDkKXbUgE5bEjImyDJVSdxQgIuYZipo2LGQ7E4G zJg+1GaYd8wA6VnxiK2Q/pwKCWjiW2D1NrAouVfNN2cyawVdMkh8NsgaHyGDmgVh 9hsKxquaXAWKkqj8T/NIPUXvOCbKlFlTTl5Aqmj4KEM4Y5bPlMuOmkp6oFApaGWn k2f6c6GO8tSzdXVfMjus7jLeXIz1qIU+4YPi8N/vErnk05miFKo6rCXUFJV3BVDs Hbpnir9ufWl2H0Q3SG0otxqtj5Mwg9j7fB7iVQOudbYDlW8PGKfV01c9KYyLrgtY 9wFy1204AS+MsoGaWMA12dmhZeBaypm0FND85gVs0AsTRBrEsi7zVdhauOXpGZcg GHoUV+LIoWSHBjsaU+97aflH2+8la+zyDNVdzpBmik3sxlT9Xh8KffJOOHhkyy90 NQKeZ3lB+52GdXCh31MrAJz2huPESFAcLa+18mU+i8rxeYZYLh9/9QQMJmZyZFBT myP8Oj/2EGWRMCpH+D2NMxEZWKvqLuXjffLirr6pF3jwI6xMsCQzq7OmR+1pR2DL ijrM+EtzEDEOeog+HTbC
=LzmU
-----END PGP SIGNATURE-----

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Signature · 2 lines
Regards
Samuel