From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] [meta-oe] giflib: Move to OE-Core
Date: Thu, 22 Mar 2012 10:28:59 +0100 [thread overview]
Message-ID: <20120322092859.GE4010@jama.jama.net> (raw)
In-Reply-To: <CAGiJk9cG0mySg454zxYS8VJLc9etr2jAAxxtBSMbN9boq0EnRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2392 bytes --]
On Thu, Mar 22, 2012 at 10:24:38AM +0100, Samuel Stirtzel wrote:
> 2012/3/21 Koen Kooi <koen@dominion.thruhere.net>:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Op 21-03-12 15:17, Samuel Stirtzel schreef:
> >> Signed-off-by: Samuel Stirtzel <s.stirtzel@googlemail.com>
> >
> > 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?
why not add meta-oe dependency to meta-kde/README?
> > -----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
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
>
> --
> Regards
> Samuel
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-03-22 9:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 14:17 [PATCH] [meta-oe] giflib: Move to OE-Core Samuel Stirtzel
2012-03-21 14:21 ` Samuel Stirtzel
2012-03-21 21:09 ` Koen Kooi
2012-03-22 9:24 ` Samuel Stirtzel
2012-03-22 9:28 ` Martin Jansa [this message]
2012-03-22 9:35 ` Samuel Stirtzel
2012-03-22 9:40 ` Eric Bénard
2012-03-22 9:42 ` Koen Kooi
2012-03-22 9:45 ` Eric Bénard
2012-03-22 10:02 ` Koen Kooi
2012-03-22 16:04 ` Khem Raj
2012-03-22 10:12 ` Samuel Stirtzel
2012-03-22 11:28 ` Koen Kooi
2012-03-22 11:38 ` Samuel Stirtzel
2012-03-22 12:10 ` Koen Kooi
2012-03-22 12:36 ` Samuel Stirtzel
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=20120322092859.GE4010@jama.jama.net \
--to=martin.jansa@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