Patchwork evtest: Add evtest 1.30 support

login
register
mail settings
Submitter Daiane Angolini
Date May 16, 2012, 7:51 p.m.
Message ID <1337197900-23107-1-git-send-email-daiane.angolini@freescale.com>
Download mbox | patch
Permalink /patch/27851/
State New
Headers show

Comments

Daiane Angolini - May 16, 2012, 7:51 p.m.
Port recipe from Meta-OE at 4bf0e7e02544e9ffa54aa0ead966c411d7dbd0be
and update to version 1.30 using FreeDesktop GIT as source.

Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 meta/recipes-support/evtest/evtest_1.30.bb |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)
 create mode 100644 meta/recipes-support/evtest/evtest_1.30.bb
Koen Kooi - May 16, 2012, 8:55 p.m.
Op 16 mei 2012 om 21:51 heeft Daiane Angolini <daiane.angolini@freescale.com> het volgende geschreven:

> Port recipe from Meta-OE at 4bf0e7e02544e9ffa54aa0ead966c411d7dbd0be
> and update to version 1.30 using FreeDesktop GIT as source.

Why bloat oe-core? Nothing is using it oe-core


> 
> Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> meta/recipes-support/evtest/evtest_1.30.bb |   14 ++++++++++++++
> 1 files changed, 14 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-support/evtest/evtest_1.30.bb
> 
> diff --git a/meta/recipes-support/evtest/evtest_1.30.bb b/meta/recipes-support/evtest/evtest_1.30.bb
> new file mode 100644
> index 0000000..222d839
> --- /dev/null
> +++ b/meta/recipes-support/evtest/evtest_1.30.bb
> @@ -0,0 +1,14 @@
> +DESCRIPTION = "Simple tool for input event debugging."
> +HOMEPAGE = "http://people.freedesktop.org/~whot/evtest/"
> +AUTHOR = "Vojtech Pavlik <vojtech@suse.cz>"
> +SECTION = "console/utils"
> +DEPENDS = "libxml2"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
> +
> +SRCREV = "e7dd232287764c0533ea89247ff907f350a12016"
> +SRC_URI = "git://anongit.freedesktop.org/evtest;protocol=git"
> +S = "${WORKDIR}/git"
> +
> +inherit autotools
> +
> -- 
> 1.7.5.4
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Otavio Salvador - May 16, 2012, 8:59 p.m.
On Wed, May 16, 2012 at 5:55 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Op 16 mei 2012 om 21:51 heeft Daiane Angolini <daiane.angolini@freescale.com> het volgende geschreven:
>> Port recipe from Meta-OE at 4bf0e7e02544e9ffa54aa0ead966c411d7dbd0be
>> and update to version 1.30 using FreeDesktop GIT as source.
>
> Why bloat oe-core? Nothing is using it oe-core

Have it in oe-core allow for inclusion of it with other test utilities
and easier to use for Yocto people. Why do you object in have it
there?
Koen Kooi - May 16, 2012, 9:06 p.m.
Op 16 mei 2012, om 22:59 heeft Otavio Salvador het volgende geschreven:

> On Wed, May 16, 2012 at 5:55 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Op 16 mei 2012 om 21:51 heeft Daiane Angolini <daiane.angolini@freescale.com> het volgende geschreven:
>>> Port recipe from Meta-OE at 4bf0e7e02544e9ffa54aa0ead966c411d7dbd0be
>>> and update to version 1.30 using FreeDesktop GIT as source.
>> 
>> Why bloat oe-core? Nothing is using it oe-core
> 
> Have it in oe-core allow for inclusion of it with other test utilities
> and easier to use for Yocto people. Why do you object in have it
> there?

OE-core is too big already, it needs to get *smaller*, not bigger.
Otavio Salvador - May 16, 2012, 9:24 p.m.
On Wed, May 16, 2012 at 6:06 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Op 16 mei 2012, om 22:59 heeft Otavio Salvador het volgende geschreven:
>> On Wed, May 16, 2012 at 5:55 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>> Op 16 mei 2012 om 21:51 heeft Daiane Angolini <daiane.angolini@freescale.com> het volgende geschreven:
>>>> Port recipe from Meta-OE at 4bf0e7e02544e9ffa54aa0ead966c411d7dbd0be
>>>> and update to version 1.30 using FreeDesktop GIT as source.
>>>
>>> Why bloat oe-core? Nothing is using it oe-core
>>
>> Have it in oe-core allow for inclusion of it with other test utilities
>> and easier to use for Yocto people. Why do you object in have it
>> there?
>
> OE-core is too big already, it needs to get *smaller*, not bigger.

And where do you think it ought to be then? test and debug utilities
for common stuff seems very commonly need to be in oe-core IMO.
Khem Raj - May 16, 2012, 9:34 p.m.
On Wed, May 16, 2012 at 1:59 PM, Otavio Salvador
<otavio@ossystems.com.br> wrote:
>
> Have it in oe-core allow for inclusion of it with other test utilities
> and easier to use for Yocto people. Why do you object in have it
> there?

if it can be said that its very common piece then it could go into OE-Core
but if its just for usability choosing a proper non OE-Core layer is
the right thing
Otavio Salvador - May 16, 2012, 9:42 p.m.
On Wed, May 16, 2012 at 6:34 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Wed, May 16, 2012 at 1:59 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>>
>> Have it in oe-core allow for inclusion of it with other test utilities
>> and easier to use for Yocto people. Why do you object in have it
>> there?
>
> if it can be said that its very common piece then it could go into OE-Core
> but if its just for usability choosing a proper non OE-Core layer is
> the right thing

Ok; well said but how do you qualify it?

evtest is very nice to have around when debugging stuff and suit very
well for a bring-up image for BSPs and like, It seems like a good
addition for me and that's why I have said to Daiane to send it to
oe-core. It is a debug and test utility and as it is generic and non
architecture or board dependant, oe-core seemed the right place for
it.
Khem Raj - May 16, 2012, 9:46 p.m.
On Wed, May 16, 2012 at 2:42 PM, Otavio Salvador
<otavio@ossystems.com.br> wrote:
> Ok; well said but how do you qualify it?
>
> evtest is very nice to have around when debugging stuff and suit very
> well for a bring-up image for BSPs and like, It seems like a good
> addition for me and that's why I have said to Daiane to send it to
> oe-core. It is a debug and test utility and as it is generic and non
> architecture or board dependant, oe-core seemed the right place for
> it.

that kind of explanations will make its case to get into OE-Core however I share
Koen's sentiments too where we should try to keep OE-Core thin. So if we discuss
the inclusion case thoroughly we will be able to make good decisions
on what should
go in into OE-Core.
I would be interested to know what others who use this utility think
Koen Kooi - May 17, 2012, 7:44 a.m.
Op 16 mei 2012, om 23:46 heeft Khem Raj het volgende geschreven:

> On Wed, May 16, 2012 at 2:42 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> Ok; well said but how do you qualify it?
>> 
>> evtest is very nice to have around when debugging stuff and suit very
>> well for a bring-up image for BSPs and like, It seems like a good
>> addition for me and that's why I have said to Daiane to send it to
>> oe-core. It is a debug and test utility and as it is generic and non
>> architecture or board dependant, oe-core seemed the right place for
>> it.
> 
> that kind of explanations will make its case to get into OE-Core however I share
> Koen's sentiments too where we should try to keep OE-Core thin. So if we discuss
> the inclusion case thoroughly we will be able to make good decisions
> on what should
> go in into OE-Core.
> I would be interested to know what others who use this utility think

Let's make a deal: new recipes will only be accepted into oe-core after sato has been removed from the oe-core layer.
Otavio Salvador - May 17, 2012, 7:54 a.m.
On Thu, May 17, 2012 at 4:44 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Let's make a deal: new recipes will only be accepted into oe-core after sato has been removed from the oe-core layer.

LOL; No! I'd like to have it in oe-core before the end of World in
December 21th ;)
Daiane Angolini - May 17, 2012, 12:47 p.m.
On Thu, May 17, 2012 at 4:44 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:

> Let's make a deal: new recipes will only be accepted into oe-core after sato has been removed from the oe-core layer.

Ok, I understand.

Could you, please, point me the right place/layer it should be included?



Daiane Angolini
Koen Kooi - May 17, 2012, 1:15 p.m.
Op 17 mei 2012, om 14:47 heeft Daiane Angolini het volgende geschreven:

> On Thu, May 17, 2012 at 4:44 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> 
>> Let's make a deal: new recipes will only be accepted into oe-core after sato has been removed from the oe-core layer.
> 
> Ok, I understand.
> 
> Could you, please, point me the right place/layer it should be included?

meta-oe

Patch

diff --git a/meta/recipes-support/evtest/evtest_1.30.bb b/meta/recipes-support/evtest/evtest_1.30.bb
new file mode 100644
index 0000000..222d839
--- /dev/null
+++ b/meta/recipes-support/evtest/evtest_1.30.bb
@@ -0,0 +1,14 @@ 
+DESCRIPTION = "Simple tool for input event debugging."
+HOMEPAGE = "http://people.freedesktop.org/~whot/evtest/"
+AUTHOR = "Vojtech Pavlik <vojtech@suse.cz>"
+SECTION = "console/utils"
+DEPENDS = "libxml2"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
+
+SRCREV = "e7dd232287764c0533ea89247ff907f350a12016"
+SRC_URI = "git://anongit.freedesktop.org/evtest;protocol=git"
+S = "${WORKDIR}/git"
+
+inherit autotools
+