Op 22 mrt. 2012, om 09:48 heeft Samuel Stirtzel het volgende geschreven: > 2012/3/21 Koen Kooi <k...@dominion.thruhere.net>: >> >> Op 21 mrt. 2012, om 20:42 heeft Saul Wold het volgende geschreven: >> >>> On 03/21/2012 07:25 AM, Samuel Stirtzel wrote: >>>> * This move will allow the testing of meta-kde for users without >>>> meta-openembedded. >>>> >>> So what other layers are using giflib? >>> >>> Your suggesting that we need to have it in oe-core so people don't need to >>> add the meta-openembedded layer when using meta-kde? >>> >>> I am just trying to get more data before making a decision. >> >> Let's put everything in oe-core! > > Otherwise it would require to maintain a redundant copy of giflib in meta-kde.
I don't think you get the concept of layers and keeping non-core stuff out of oe-core. > Alternative suggestions are welcome. > > > A grep shows that not many recipes depend on giflib: > - > samuel@s-stirtzel-linux:/work/oe-core/setup-scripts/sources$ grep -r 'giflib' > * > meta-java/recipes-core/openjdk/openjdk-6-common.inc:DEPENDS = "giflib > libpng jpeg cups \ > meta-java/recipes-core/icedtea/icedtea6-native.inc: > freetype-native zlib-native giflib-native jpeg-native \ > meta-kde/recipes-kde-base/kdelibs4_git.bb:DEPENDS = "automoc4-native > strigi libdbusmenu-qt soprano shared-desktop-ontologies dbus giflib > attica jpeg libpng bzip2 libpcre perl-native" > meta-openembedded/meta-efl/recipes-efl/efl/evas.inc:DEPENDS = "librsvg > eina eet freetype jpeg libpng virtual/libx11 libxext libxrender > fontconfig libfribidi giflib" > - > > Any reason against the move? The whole layering concept _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core