Skip to contentSkip to conversation

giflib: Move to OE-Core

PATCH In review Samuel Stirtzel 5 participants 16 messages Mar 21, 2012 – Mar 22, 2012

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 giflib: Move to OE-Core

---
 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

Seems like my commit message got lost sorry,
this was requested from a tester of meta-kde who doesn't use meta-openembedded.

2012/3/21 Samuel Stirtzel <[email protected]>:

Quoted 35 lines

---
 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 -21
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"
--

1.7.5.4

Signature · 2 lines
Regards
Samuel
#2 lore raw
In reply to Samuel Stirtzel

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

Op 21-03-12 15:17, Samuel Stirtzel schreef:

Quoted 1 line

OE-core needs to slim down, not get fatter. You are basically saying "layer suck, let's move back to oe-classic"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJPakOkAAoJEHZqAkdh1vT6zyQP/R7/viIEf4trbFzR3ZaD2cRd D4U4q7eDF5DM/fC85yoLBj7byBfryB/I2JWDir9YOAcGgaBysvpL5vApTWFt1hJZ MOc3NFNdIsALL/jnMzjmY4OB5bIAYHj4nC0XGiRj6CuEvkyz6IueAAR3k2O6NU64 L32Ou0iGD0GKg6gl8LSBfixVKYAjIFfehP5rWv1L0P7cJiYmVy4Gj7CalmmRpPZz zMhmwoUze4dIx9z6X5WSIXs44aBOFs3MZjtYRfBQsUDkjBheLWI5tMIekhFX0Ega wKjU9GUwerPzI0oI2DG+9n7nS1wlBJesrHAQKh3pwCWRC19NQuqFjArdaF80DwPk ZHZNnTzB5Dd/NbPcSkRG5V0DAFYB54Xty6A2w7ONbPoQs5h3vjS4g8V560Kvgqaa O/efrZi2VgYA/1RAaz7COjNkMF/OBeH9aE9oRNPweOBYcwMFzhbrTEXPUL/pZ7gg 5oI0JdJj5lmqi6q9+jk8hDVJvYIkM45l9xqy6nDnIa0tUnDTzCRxj+jr7LEyPp/R p+/6GO5aPG8S4JPbmgFbmJN7hrLzNyg6JS962VVYiOhw0cIVwkj/hX+9oYPE4pRe AHXoBtWrfflkL4RIadYI64uMJHNpHzfuzd6+0JljL8sA969nh36GXsd4OwMdUx6b AVqAIeCDYo30C3i9BXRL
=1Xye
-----END PGP SIGNATURE-----

#3 lore raw

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

Quoted 8 lines

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

Op 21-03-12 15:17, Samuel Stirtzel schreef:

Quoted 1 line

OE-core needs to slim down, not get fatter. You are basically saying "layer suck, let's move back to oe-classic"

That is definitively not what I want to say.
In my point of view there is no value in maintaining an existing recipe redundantly in meta-oe and kde-core or anywhere else.

And IMHO we need to get over this, how is it supposed to work? Should I make a meta-devtools layer?
Or should I copy giflib from meta-oe and all recipes from oe-core that meta-kde depends on over to my own layer?

Quoted 24 lines

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

iQIcBAEBAgAGBQJPakOkAAoJEHZqAkdh1vT6zyQP/R7/viIEf4trbFzR3ZaD2cRd D4U4q7eDF5DM/fC85yoLBj7byBfryB/I2JWDir9YOAcGgaBysvpL5vApTWFt1hJZ MOc3NFNdIsALL/jnMzjmY4OB5bIAYHj4nC0XGiRj6CuEvkyz6IueAAR3k2O6NU64 L32Ou0iGD0GKg6gl8LSBfixVKYAjIFfehP5rWv1L0P7cJiYmVy4Gj7CalmmRpPZz zMhmwoUze4dIx9z6X5WSIXs44aBOFs3MZjtYRfBQsUDkjBheLWI5tMIekhFX0Ega wKjU9GUwerPzI0oI2DG+9n7nS1wlBJesrHAQKh3pwCWRC19NQuqFjArdaF80DwPk ZHZNnTzB5Dd/NbPcSkRG5V0DAFYB54Xty6A2w7ONbPoQs5h3vjS4g8V560Kvgqaa O/efrZi2VgYA/1RAaz7COjNkMF/OBeH9aE9oRNPweOBYcwMFzhbrTEXPUL/pZ7gg 5oI0JdJj5lmqi6q9+jk8hDVJvYIkM45l9xqy6nDnIa0tUnDTzCRxj+jr7LEyPp/R p+/6GO5aPG8S4JPbmgFbmJN7hrLzNyg6JS962VVYiOhw0cIVwkj/hX+9oYPE4pRe AHXoBtWrfflkL4RIadYI64uMJHNpHzfuzd6+0JljL8sA969nh36GXsd4OwMdUx6b AVqAIeCDYo30C3i9BXRL
=1Xye
-----END PGP SIGNATURE-----

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

Signature · 2 lines
Regards
Samuel
#4 lore raw
Quoted 15 lines · Samuel Stirtzel

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

Quoted 8 lines

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

Op 21-03-12 15:17, Samuel Stirtzel schreef:

Quoted 1 line

OE-core needs to slim down, not get fatter. You are basically saying "layer suck, let's move back to oe-classic"

That is definitively not what I want to say.
In my point of view there is no value in maintaining an existing recipe redundantly in meta-oe and kde-core or anywhere else.

Quoted 4 lines

And IMHO we need to get over this, how is it supposed to work? Should I make a meta-devtools layer?
Or should I copy giflib from meta-oe and all recipes from oe-core that meta-kde depends on over to my own layer?

why not add meta-oe dependency to meta-kde/README?

Quoted 35 lines
Quoted 24 lines

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

iQIcBAEBAgAGBQJPakOkAAoJEHZqAkdh1vT6zyQP/R7/viIEf4trbFzR3ZaD2cRd D4U4q7eDF5DM/fC85yoLBj7byBfryB/I2JWDir9YOAcGgaBysvpL5vApTWFt1hJZ MOc3NFNdIsALL/jnMzjmY4OB5bIAYHj4nC0XGiRj6CuEvkyz6IueAAR3k2O6NU64 L32Ou0iGD0GKg6gl8LSBfixVKYAjIFfehP5rWv1L0P7cJiYmVy4Gj7CalmmRpPZz zMhmwoUze4dIx9z6X5WSIXs44aBOFs3MZjtYRfBQsUDkjBheLWI5tMIekhFX0Ega wKjU9GUwerPzI0oI2DG+9n7nS1wlBJesrHAQKh3pwCWRC19NQuqFjArdaF80DwPk ZHZNnTzB5Dd/NbPcSkRG5V0DAFYB54Xty6A2w7ONbPoQs5h3vjS4g8V560Kvgqaa O/efrZi2VgYA/1RAaz7COjNkMF/OBeH9aE9oRNPweOBYcwMFzhbrTEXPUL/pZ7gg 5oI0JdJj5lmqi6q9+jk8hDVJvYIkM45l9xqy6nDnIa0tUnDTzCRxj+jr7LEyPp/R p+/6GO5aPG8S4JPbmgFbmJN7hrLzNyg6JS962VVYiOhw0cIVwkj/hX+9oYPE4pRe AHXoBtWrfflkL4RIadYI64uMJHNpHzfuzd6+0JljL8sA969nh36GXsd4OwMdUx6b AVqAIeCDYo30C3i9BXRL
=1Xye
-----END PGP SIGNATURE-----

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

Signature · 7 lines
Regards
Samuel

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#5 lore raw

2012/3/22 Martin Jansa <[email protected]>:

Quoted 16 lines · Samuel Stirtzel
Quoted 15 lines

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

Quoted 8 lines

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

Op 21-03-12 15:17, Samuel Stirtzel schreef:

Quoted 1 line

OE-core needs to slim down, not get fatter. You are basically saying "layer suck, let's move back to oe-classic"

That is definitively not what I want to say.
In my point of view there is no value in maintaining an existing recipe redundantly in meta-oe and kde-core or anywhere else.

Quoted 6 lines
Quoted 4 lines

And IMHO we need to get over this, how is it supposed to work? Should I make a meta-devtools layer?
Or should I copy giflib from meta-oe and all recipes from oe-core that meta-kde depends on over to my own layer?

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1].
But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

Quoted 37 lines
Quoted 28 lines
Quoted 21 lines

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

iQIcBAEBAgAGBQJPakOkAAoJEHZqAkdh1vT6zyQP/R7/viIEf4trbFzR3ZaD2cRd D4U4q7eDF5DM/fC85yoLBj7byBfryB/I2JWDir9YOAcGgaBysvpL5vApTWFt1hJZ MOc3NFNdIsALL/jnMzjmY4OB5bIAYHj4nC0XGiRj6CuEvkyz6IueAAR3k2O6NU64 L32Ou0iGD0GKg6gl8LSBfixVKYAjIFfehP5rWv1L0P7cJiYmVy4Gj7CalmmRpPZz zMhmwoUze4dIx9z6X5WSIXs44aBOFs3MZjtYRfBQsUDkjBheLWI5tMIekhFX0Ega wKjU9GUwerPzI0oI2DG+9n7nS1wlBJesrHAQKh3pwCWRC19NQuqFjArdaF80DwPk ZHZNnTzB5Dd/NbPcSkRG5V0DAFYB54Xty6A2w7ONbPoQs5h3vjS4g8V560Kvgqaa O/efrZi2VgYA/1RAaz7COjNkMF/OBeH9aE9oRNPweOBYcwMFzhbrTEXPUL/pZ7gg 5oI0JdJj5lmqi6q9+jk8hDVJvYIkM45l9xqy6nDnIa0tUnDTzCRxj+jr7LEyPp/R p+/6GO5aPG8S4JPbmgFbmJN7hrLzNyg6JS962VVYiOhw0cIVwkj/hX+9oYPE4pRe AHXoBtWrfflkL4RIadYI64uMJHNpHzfuzd6+0JljL8sA969nh36GXsd4OwMdUx6b AVqAIeCDYo30C3i9BXRL
=1Xye
-----END PGP SIGNATURE-----

Quoted 4 lines

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

Quoted 8 lines

--
Regards
Samuel

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

Quoted 8 lines

--
Martin 'JaMa' Jansa     jabber: [email protected]

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

[1] https://gitorious.org/openembedded-core-layers/meta-kde/blobs/master/README#line4

Signature · 2 lines
Regards
Samuel
#6 lore raw
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1].
But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

can you describe this use case so that meta-oe gets a chance to adapt.

One problem I can see with meta-oe is the fact that it makes changes to the oe-core toolchain : that would be great to put all the toolchain changes in a meta-toolchain (but I think that's what is scheduled with meta-linaro).

Eric

#7 lore raw

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

Op 22-03-12 10:40, Eric Bénard schreef:

Quoted 10 lines
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1]. But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

Quoted 6 lines

can you describe this use case so that meta-oe gets a chance to adapt.

One problem I can see with meta-oe is the fact that it makes changes to the oe-core toolchain : that would be great to put all the toolchain changes in a meta-toolchain (but I think that's what is scheduled with meta-linaro).

In the mean time I bet Khem would love to have people sending patches to move the toolchain bits to a meta-toolchain layer inside the meta-openembedded repo.

regards,

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

iQIbBAEBAgAGBQJPavQHAAoJEHZqAkdh1vT6IGQP+LLOR/8GoZ3Fplqwacx5g0Nf 9CTeHg1Pz+owg6yJ8H0UiQmfks3R5P6mq19vkvxEjXqYMBmv+Apk5O+qwWxLgfgQ 2Bn7v5zywQ9fiIa8NEqDtECFFnYUcgxlOFT6AUTDoN/ZqKXjJkbM8jADkjNGCBWD 0tHSk2V+eELujPAhkboxV+977aUS4vyETUahIr0rWGdUKJbNEse5yN2r6UFxNL8f 7cffRnurY9qhD9Ebm7QZ1AI8shoRoG3Z4SRnFH4Hf5xO7rr7g8M13ItLF6u6GnZk TZUlGRcMUmAgx1CW16LLfWKPh4s+XACoq1QPJe5LvN0UPlE0q2QOi6254PbkaJSs 2mk7FgaZUN0btBo5XmKfa7YMyh3VMIVhyvj2VPK+HY4Yn9lUcJLlqi98LyZ3kYpA KwjVJG66XoV5NCUOOIEBriTC+d+keHwdhAPYp6vQMLIu5B4vJQCb/9Vpf7yrkydE wHYTyUFiXF9BSfRn2k85dYOCtg9e25u0ev4O8JNFiLWM5xfTi1T9WbS4h+duC28D ukklNHsyJXOL8eT0OzGO8Z88ldRyOpLrcnXmgBw8KVQmWNZAX/TT2+pa2t2FOwvQ dFB1ay3+AxEHkrYyaeXj5bNQ9ugYchb7UWGh9/2EzUsSMWhYcJi6uWvxex0A/rp0 MnufdpP7bO3CyXxl4Gk=
=Rz9p
-----END PGP SIGNATURE-----

#8 lore raw
Quoted 16 lines · Koen Kooi

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

Op 22-03-12 10:40, Eric Bénard schreef:

Quoted 12 lines
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1]. But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

can you describe this use case so that meta-oe gets a chance to adapt.

Quoted 9 lines
Quoted 4 lines

One problem I can see with meta-oe is the fact that it makes changes to the oe-core toolchain : that would be great to put all the toolchain changes in a meta-toolchain (but I think that's what is scheduled with meta-linaro).

In the mean time I bet Khem would love to have people sending patches to move the toolchain bits to a meta-toolchain layer inside the meta-openembedded repo.

ok so expect patches by this weekend for this point.

Eric

#9 lore raw

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

Op 22-03-12 10:45, Eric Bénard schreef:

Quoted 24 lines
Quoted 21 lines · Koen Kooi

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

Op 22-03-12 10:40, Eric Bénard schreef:

Quoted 17 lines
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1]. But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

can you describe this use case so that meta-oe gets a chance to adapt.

One problem I can see with meta-oe is the fact that it makes changes to the oe-core toolchain : that would be great to put all the toolchain changes in a meta-toolchain (but I think that's what is scheduled with meta-linaro).

Quoted 5 lines
Quoted 4 lines

In the mean time I bet Khem would love to have people sending patches to move the toolchain bits to a meta-toolchain layer inside the meta-openembedded repo.

ok so expect patches by this weekend for this point.

I sent an RFC patch to get some more peoples attention :) -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJPavjLAAoJEHZqAkdh1vT6wU4P/ioH3asxsreEWPmdYsYP+K+Q JaLTLlXYqv6asne9a7+Gmro7WaHboalmrUQgISgWNjF7iTrBuKAby2zV1PjC1vJg eXkpLv25xSdFVlbhHSl46iJvzBlXhFKqodxMwYavgMD+XGS+1ABaYlr5vgZsPdVR ZDl036PrRhnLN8qYhYy7jatTN7obndwH6DUycc6HbQ/OAg4KDYQnZQ+PSuChfhT/ HIs721q7JOV4fBGEnx2lEm12JW3jy/4SJH4WFK44hCQ6YcHt7dkHWYH7o+HOmO50 SRhWqLtSTTqQiG6hHoVmWHe6jWhlqsmeyYSHOHI5K80nI51ADaweppFEHe4+r2LC S6WZTN1lvJdnqCtH9aSrUNMlR/+hqLKyO/R892fv9R2wTF1ZVMW3eJHGnr9LfCBq b77xdq4ErniMWFoP7Oyd/GocHmH7K5NJgFqwMgIRokVmUxU+Y+EzEZoEeR2Ju7So nancX5XScBRspz4zZDDZkQCBKycG13iTUoT/56ZXelP75y7f42vK9nvHvnwJu+TL 9yn2dCK1bS9e/3cc+yG5/qRlJwLmqeSxfPtrasgcaH0BI+yIKL9CpoYee2Rj6i7P ZszerMxGBvQEXUoQ5yX3VMC2hrGGJUVoqCNK5UtQUipLOZh3pYNRTB/ThXW3t37h 8bVIjvb5ptE9XAD7ypYt
=dGZ8
-----END PGP SIGNATURE-----

#10 lore raw
In reply to Koen Kooi
Quoted 4 lines · Koen Kooi

In the mean time I bet Khem would love to have people sending patches to move the toolchain bits to a meta-toolchain layer inside the meta-openembedded repo.

yes please.

#11 lore raw
In reply to Eric Bénard

2012/3/22 Eric Bénard <[email protected]>:

Quoted 11 lines
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1].
But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

can you describe this use case so that meta-oe gets a chance to adapt.

Since I have the common use case of the installation provided from the setup-scripts and I don't know the exact use case,
I cannot provide this information myself right now.

This "only" involves me as I was requested to add a copy of the giflib recipe to meta-kde,
to support the testing of meta-kde with a non meta-oe use case.

Since I don't think that recipe redundancy will be of any use, I suggested to move giflib to oe-core.

Quoted 12 lines

One problem I can see with meta-oe is the fact that it makes changes to the oe-core toolchain : that would be great to put all the toolchain changes in a meta-toolchain (but I think that's what is scheduled with meta-linaro).

Eric

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

Signature · 2 lines
Regards
Samuel
#12 lore raw

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

Op 22-03-12 11:12, Samuel Stirtzel schreef:

Quoted 11 lines

2012/3/22 Eric Bénard <[email protected]>:

Quoted 10 lines
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1]. But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

Quoted 5 lines
Quoted 1 line

can you describe this use case so that meta-oe gets a chance to adapt.

Since I have the common use case of the installation provided from the setup-scripts and I don't know the exact use case, I cannot provide this information myself right now.

So you can't explain why it should move to oe-core, that should be enough to NAK this patch without even looking at it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJPawy/AAoJEHZqAkdh1vT6cdAP/3CIpSE6k6BOPHXEri6hgLU4 kfQhs6GKHRxgyCB63jDWJ1EShrErKUrCksWMAXO6p7tBniuMk8X5mJmQ4mBfHH9b 0yTu5bPFxB/zsK0lFqoOfWMOuwaJLZJQCuEQLJP4VvlVxexb5sZMbzMvudh+pGwQ DZEgDGbTF+hUrcxu0Rjxug9UXJa4nqfiCJ7ShKy3U2+ichZnr4tU9YfUl5ZGoofT W/xtJOBwEKogGB0KxIb2tphtChpoA8rPMy5WvRqlJ39lDsUOdOHUl5/Vu83Czpee ynFe5aRxYjsz0NUovuiBc5SUwVCwqJApR164FCFIkhHg7l1G7OJelSrn1+oqA62f fX6MTno5dYpaWImx2KiGqHOKqJF4wo+C0QqGNFBYde4Yu9Xu2Wdx/GQnycov6TOf deQtQnDHFZ4K4oaT4ptQvzcb0qN4KU5f3scCjSAR9SMNfPjjuaI7wmlRD8UwGB61 s1oipV+SNE9icv8qSGbV9gw1Bo+B9w4AHRZllt9tdsDhnoMldBot7Fhc+FuW0MbH uFOmzi4R1j9lXmoh5pcFkmZKSYra4/UhU9DkwGZ4IZzEMCE4cxfwDc3MYGyPPOTE 0oMbq01pmAfPsio7gQ1bE73WC0JWBhKfbFJ7KxF3mH0oC1+mrBw9y2Al+7Zd0o7P B+y8ooG5B0ELZdWvczXO
=EYSh
-----END PGP SIGNATURE-----

#13 lore raw

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

Quoted 15 lines

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

Op 22-03-12 11:12, Samuel Stirtzel schreef:

Quoted 11 lines

2012/3/22 Eric Bénard <[email protected]>:

Quoted 10 lines
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1]. But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

can you describe this use case so that meta-oe gets a chance to adapt.

Since I have the common use case of the installation provided from the setup-scripts and I don't know the exact use case, I cannot provide this information myself right now.

So you can't explain why it should move to oe-core, that should be enough to NAK this patch without even looking at it.

If the explanation that an user group that has another use case than you won't be enought then NAK it.

Quoted 24 lines

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

iQIcBAEBAgAGBQJPawy/AAoJEHZqAkdh1vT6cdAP/3CIpSE6k6BOPHXEri6hgLU4 kfQhs6GKHRxgyCB63jDWJ1EShrErKUrCksWMAXO6p7tBniuMk8X5mJmQ4mBfHH9b 0yTu5bPFxB/zsK0lFqoOfWMOuwaJLZJQCuEQLJP4VvlVxexb5sZMbzMvudh+pGwQ DZEgDGbTF+hUrcxu0Rjxug9UXJa4nqfiCJ7ShKy3U2+ichZnr4tU9YfUl5ZGoofT W/xtJOBwEKogGB0KxIb2tphtChpoA8rPMy5WvRqlJ39lDsUOdOHUl5/Vu83Czpee ynFe5aRxYjsz0NUovuiBc5SUwVCwqJApR164FCFIkhHg7l1G7OJelSrn1+oqA62f fX6MTno5dYpaWImx2KiGqHOKqJF4wo+C0QqGNFBYde4Yu9Xu2Wdx/GQnycov6TOf deQtQnDHFZ4K4oaT4ptQvzcb0qN4KU5f3scCjSAR9SMNfPjjuaI7wmlRD8UwGB61 s1oipV+SNE9icv8qSGbV9gw1Bo+B9w4AHRZllt9tdsDhnoMldBot7Fhc+FuW0MbH uFOmzi4R1j9lXmoh5pcFkmZKSYra4/UhU9DkwGZ4IZzEMCE4cxfwDc3MYGyPPOTE 0oMbq01pmAfPsio7gQ1bE73WC0JWBhKfbFJ7KxF3mH0oC1+mrBw9y2Al+7Zd0o7P B+y8ooG5B0ELZdWvczXO
=EYSh
-----END PGP SIGNATURE-----

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

Signature · 2 lines
Regards
Samuel
#14 lore raw

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

Op 22-03-12 12:38, Samuel Stirtzel schreef:

Quoted 16 lines

2012/3/22 Koen Kooi <[email protected]>: Op 22-03-12 11:12, Samuel Stirtzel schreef:

Quoted 14 lines
Quoted 14 lines
Quoted 14 lines

2012/3/22 Eric Bénard <[email protected]>:

Quoted 12 lines
Quoted 8 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

It is already listed as dependency [1]. But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

can you describe this use case so that meta-oe gets a chance to adapt.

Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

Since I have the common use case of the installation provided from the setup-scripts and I don't know the exact use case, I cannot provide this information myself right now.

So you can't explain why it should move to oe-core, that should be enough to NAK this patch without even looking at it.

Quoted 1 line

If the explanation that an user group that has another use case

No, an *alledged* user group that *might* have an *alledged* use case for which you say yourself you cannot provide the information. That is what I'm complaining about, the degrees of hearsay and hypotheticals in your argument.

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

iQIcBAEBAgAGBQJPaxajAAoJEHZqAkdh1vT6+PgP/13/oayQIuLVdpEx2uslB0LZ XV5ctwGBoPW6VCIXg/GpTe0BzdIe8hUdnCLZt0gLf2UMN44Wy3RNVZ86000s0GM3 R1/cJ+qNCjrjvNQtUYazG5fklvOk1MtHQnhvyznmkhrSYdaPsMQeeZHkdGey35X6 MZavWe0ufOdKwJG7xgRb5LETduk8IgK6l7sYXr8lIvqq+TRzOqwkDO8ny1cQz1O6 yKFPDisAQGsn4IKwwxPnpoS9/78y8HK4oo6jq5KWoLkQHIGmqe224mTTv7F+EV0b Ph/TwCQO6oNFLj64oaW9lQpBO1sSTBAMj51Oxvs8cHdQsZeswiAYH9qm8rbrNlRy QM0QRPxx6aB1K242ZcQfAlMXjgiw0akiMxtxMknJJTzVIpXINV+ZLn2TxsRVHRh+ buuL7HCOiwGYXXzheXLaX4fS+Ctf4i6y0oI8o1F3vscAcj5z7n0YCEG0xu4wWddd bVbKQ/NHAnkdEE2PKYoP3jJirzFAfh/1X2NCWgD0CJSYoNkukZ3Tx1reINHg4mW5 r3pFkaxo3B/5QaEHgo6Q8w/bGHu6toOjc3xt7yZPVp1Ita8yRxFEulrBcecd+UbO zzorKmBkJ96y98C6q2ihbo+SqrCGn/5Sx1b/8y7r70DWXyuECasdWM+5ASBmiiJs TAl4oHGfVVoedxmuD7fJ
=AxKX
-----END PGP SIGNATURE-----

#15 lore raw

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

Quoted 24 lines

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

Op 22-03-12 12:38, Samuel Stirtzel schreef:

Quoted 20 lines

2012/3/22 Koen Kooi <[email protected]>: Op 22-03-12 11:12, Samuel Stirtzel schreef:

Quoted 17 lines
Quoted 17 lines
Quoted 17 lines

2012/3/22 Eric Bénard <[email protected]>:

Quoted 5 lines
Quoted 3 lines · Samuel Stirtzel

2012/3/22 Martin Jansa <[email protected]>:

Quoted 1 line

why not add meta-oe dependency to meta-kde/README?

Quoted 7 lines
Quoted 5 lines

It is already listed as dependency [1]. But somehow it seems like that there are users, interested in testing this layer, with an use case which excludes the meta-oe layer.

can you describe this use case so that meta-oe gets a chance to adapt.

Since I have the common use case of the installation provided from the setup-scripts and I don't know the exact use case, I cannot provide this information myself right now.

Quoted 8 lines
Quoted 4 lines

So you can't explain why it should move to oe-core, that should be enough to NAK this patch without even looking at it.

Quoted 1 line

If the explanation that an user group that has another use case

No, an *alledged* user group that *might* have an *alledged* use case for which you say yourself you cannot provide the information. That is what I'm complaining about, the degrees of hearsay and hypotheticals in your argument.

Ok I will send a V2 with a proper commit message and a proper target audience / use case.

Quoted 26 lines

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

iQIcBAEBAgAGBQJPaxajAAoJEHZqAkdh1vT6+PgP/13/oayQIuLVdpEx2uslB0LZ XV5ctwGBoPW6VCIXg/GpTe0BzdIe8hUdnCLZt0gLf2UMN44Wy3RNVZ86000s0GM3 R1/cJ+qNCjrjvNQtUYazG5fklvOk1MtHQnhvyznmkhrSYdaPsMQeeZHkdGey35X6 MZavWe0ufOdKwJG7xgRb5LETduk8IgK6l7sYXr8lIvqq+TRzOqwkDO8ny1cQz1O6 yKFPDisAQGsn4IKwwxPnpoS9/78y8HK4oo6jq5KWoLkQHIGmqe224mTTv7F+EV0b Ph/TwCQO6oNFLj64oaW9lQpBO1sSTBAMj51Oxvs8cHdQsZeswiAYH9qm8rbrNlRy QM0QRPxx6aB1K242ZcQfAlMXjgiw0akiMxtxMknJJTzVIpXINV+ZLn2TxsRVHRh+ buuL7HCOiwGYXXzheXLaX4fS+Ctf4i6y0oI8o1F3vscAcj5z7n0YCEG0xu4wWddd bVbKQ/NHAnkdEE2PKYoP3jJirzFAfh/1X2NCWgD0CJSYoNkukZ3Tx1reINHg4mW5 r3pFkaxo3B/5QaEHgo6Q8w/bGHu6toOjc3xt7yZPVp1Ita8yRxFEulrBcecd+UbO zzorKmBkJ96y98C6q2ihbo+SqrCGn/5Sx1b/8y7r70DWXyuECasdWM+5ASBmiiJs TAl4oHGfVVoedxmuD7fJ
=AxKX
-----END PGP SIGNATURE-----

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

Signature · 2 lines
Regards
Samuel