All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Dinu <andrei.adrianx.dinu@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe] gypsy: added gypsy to meta-oe/recipes-connectivity
Date: Wed, 24 Oct 2012 13:41:37 +0300	[thread overview]
Message-ID: <5087C5E1.80105@intel.com> (raw)
In-Reply-To: <20121024101220.GB3269@jama.jama.net>

Should i submit a new patch with the gypsy in recipes-navigation?

I spoke to Ross Burton about the bug/patch and he suggested adding only 
the tarball, that's

why i didn't include the git recipe too.

I'm waiting for your answer.

Thanks,

Andrei Dinu

On 10/24/2012 01:12 PM, Martin Jansa wrote:
> On Wed, Oct 24, 2012 at 01:08:55PM +0300, Andrei Dinu wrote:
>> This patch is related to bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=2797.
> Ah I forgot to mention that recipes-navigation would be better directory
> for this.
>
> And you can add that updated git recipe too.
>
> Cheers,
>
>> Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com>
>> ---
>>   .../recipes-connectivity/gypsy/files/fixups.patch  |   21 +++++++++++++++++
>>   meta-oe/recipes-connectivity/gypsy/gypsy.inc       |   15 ++++++++++++
>>   meta-oe/recipes-connectivity/gypsy/gypsy_0.9.bb    |   24 ++++++++++++++++++++
>>   3 files changed, 60 insertions(+)
>>   create mode 100644 meta-oe/recipes-connectivity/gypsy/files/fixups.patch
>>   create mode 100644 meta-oe/recipes-connectivity/gypsy/gypsy.inc
>>   create mode 100644 meta-oe/recipes-connectivity/gypsy/gypsy_0.9.bb
>>
>> diff --git a/meta-oe/recipes-connectivity/gypsy/files/fixups.patch b/meta-oe/recipes-connectivity/gypsy/files/fixups.patch
>> new file mode 100644
>> index 0000000..de4d92e
>> --- /dev/null
>> +++ b/meta-oe/recipes-connectivity/gypsy/files/fixups.patch
>> @@ -0,0 +1,21 @@
>> +Upstream-Status: Inappropriate [configuration]
>> +
>> +---
>> + docs/reference/Makefile.am |    2 ++
>> + 1 file changed, 2 insertions(+)
>> +
>> +--- gypsy.orig/docs/reference/Makefile.am
>> ++++ gypsy/docs/reference/Makefile.am
>> +@@ -81,10 +81,12 @@ expand_content_files=
>> + # e.g. GTKDOC_LIBS=$(top_builddir)/gtk/$(gtktargetlib)
>> +
>> + INCLUDES=-I$(top_srcdir) $(GYPSY_CFLAGS)
>> + GTKDOC_LIBS=$(top_builddir)/gypsy/libgypsy.la $(GYPSY_LIBS)
>> +
>> ++EXTRA_DIST =
>> ++CLEANFILES =
>> + # This includes the standard gtk-doc make rules, copied by gtkdocize.
>> + include $(top_srcdir)/gtk-doc.make
>> +
>> + # Other files to distribute
>> + # e.g. EXTRA_DIST += version.xml.in
>> diff --git a/meta-oe/recipes-connectivity/gypsy/gypsy.inc b/meta-oe/recipes-connectivity/gypsy/gypsy.inc
>> new file mode 100644
>> index 0000000..0c1735e
>> --- /dev/null
>> +++ b/meta-oe/recipes-connectivity/gypsy/gypsy.inc
>> @@ -0,0 +1,15 @@
>> +SUMMARY = "GPS Multiplexing Daemon"
>> +DESCRIPTION = "Gypsy is a GPS multiplexing daemon which allows \
>> +multiple clients to access GPS data from multiple GPS sources \
>> +concurrently.  Gypsy also hides the details of parsing NMEA from the \
>> +client applications, passing the data as simple values for the clients \
>> +to use."
>> +LICENSE = "GPLv2.0 & LGPLv2.1"
>> +SECTION = "x11"
>> +DEPENDS = "glib-2.0 dbus bluez4 dbus-glib"
>> +
>> +inherit autotools pkgconfig gtk-doc
>> +
>> +EXTRA_OECONF += "--with-distro=debian"
>> +
>> +FILES_${PN} += "/usr/share/dbus-1/services/"
>> diff --git a/meta-oe/recipes-connectivity/gypsy/gypsy_0.9.bb b/meta-oe/recipes-connectivity/gypsy/gypsy_0.9.bb
>> new file mode 100644
>> index 0000000..51207c9
>> --- /dev/null
>> +++ b/meta-oe/recipes-connectivity/gypsy/gypsy_0.9.bb
>> @@ -0,0 +1,24 @@
>> +SUMMARY = "GPS Multiplexing Daemon"
>> +DESCRIPTION = "Gypsy is a GPS multiplexing daemon which allows \
>> +multiple clients to access GPS data from multiple GPS sources \
>> +concurrently.  Gypsy also hides the details of parsing NMEA from the \
>> +client applications, passing the data as simple values for the clients \
>> +to use."
>> +LICENSE = "GPLv2+ & LGPLv2+"
>> +LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
>> +                    file://COPYING.lib;md5=7fbc338309ac38fefcd64b04bb903e34 \
>> +                    file://src/main.c;beginline=1;endline=25;md5=3fe64e27e61b289b77383a54a982cbdd \
>> +                    file://gypsy/gypsy-time.h;beginline=1;endline=24;md5=06432ea19a7b6607428d04d9dadc37fd"
>> +
>> +SECTION = "x11"
>> +DEPENDS = "glib-2.0 dbus bluez4 dbus-glib libxslt"
>> +
>> +SRC_URI = "http://gypsy.freedesktop.org/releases/gypsy-${PV}.tar.gz"
>> +PR = "r1"
>> +
>> +inherit autotools pkgconfig
>> +
>> +FILES_${PN} += "/usr/share/dbus-1/system-services/"
>> +
>> +SRC_URI[md5sum] = "e2d186df9c2cc3b70a027043e22acf1a"
>> +SRC_URI[sha256sum] = "14e1cbe17351f408538e033ca370b4bf51ccf9c88744e236ddfb271904f154d6"
>> -- 
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




  reply	other threads:[~2012-10-24 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 10:08 [meta-oe] gypsy: added gypsy to meta-oe/recipes-connectivity Andrei Dinu
2012-10-24 10:12 ` Martin Jansa
2012-10-24 10:41   ` Andrei Dinu [this message]
2012-10-24 10:44     ` Martin Jansa

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=5087C5E1.80105@intel.com \
    --to=andrei.adrianx.dinu@intel.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.