Re: [oe] [2011.03-maintenance] Pull request 20120514
Am Montag, den 21.05.2012, 13:53 + schrieb Maupin, Chase: -Original Message- From: Paul Menzel [mailto:paulepan...@users.sourceforge.net] Sent: Saturday, May 19, 2012 3:59 AM […] Chase Maupin (69): gnutls: update LICENSE setting I would have liked to have split those up. Update the license and add the inherit line. I'll split this up then and regenerate the patch set. If that patch set has already been submitted to meta-oe this way, please do not spent your time doing that. If it is independent from meta-oe please do so. libtasn1: update LICENSE setting bonnie: Update LICENSE field version It would have been great to have the changed license in the commit message also. […] schroedinger: Update LICENSE field version A change in `schroedinger.inc` is preferred in my opinion. I didn't change the .inc because I did not validate all versions of schroedinger. Understood. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [2011.03-maintenance] Pull request 20120514
Dear Chase, Am Montag, den 14.05.2012, 13:09 -0500 schrieb Chase Maupin: Please pull the following commits that update the LICENSE field to list the actual license version for licenses like GPL and LGPL. These patches have previously been sent to the list with each patch identifying where it was derived from. I have also submitted patches for oe-core where appropriate. I'm looking for feedback on how to properly mark a package as having two licenses in oe-classic since causes issues. If these patches are OK then they can be pulled. If there is a better way to mark the dual licensing then I'll update them accordingly. The following changes since commit 36a56cbb69cda0c89f478e01183d61c6a66525c9: Steffen Sledz (1): icedtea6-native-1.7.10: backport S7103224 are available in the git repository at: http://arago-project.org/git/projects/arago-oe-amsdk.git update-licenses Chase Maupin (69): gnutls: update LICENSE setting I would have liked to have split those up. Update the license and add the inherit line. libtasn1: update LICENSE setting bonnie: Update LICENSE field version It would have been great to have the changed license in the commit message also. […] schroedinger: Update LICENSE field version A change in `schroedinger.inc` is preferred in my opinion. […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] midori: Add project home page info
Am Freitag, den 16.03.2012, 13:41 -0600 schrieb Gary Thomas: Signed-off-by: Gary Thomas g...@mlbassoc.com --- meta-oe/recipes-connectivity/midori/midori.inc |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/meta-oe/recipes-connectivity/midori/midori.inc b/meta-oe/recipes-connectivity/midori/midori.inc index 4c7147e..dccb3ee 100644 --- a/meta-oe/recipes-connectivity/midori/midori.inc +++ b/meta-oe/recipes-connectivity/midori/midori.inc @@ -1,4 +1,5 @@ DESCRIPTION = Midori is a lightweight web browser. +HOMEPAGE = http://www.twotoasts.de/index.php?/pages/midori_summary.html; LICENSE = LGPLv2.1 LIC_FILES_CHKSUM = file://COPYING;md5=fbc093901857fcd118f065f900982c24 Acked-by: Paul Menzel paulepan...@users.sourceforge.net Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] midori: Add project home page info
Am Sonntag, den 18.03.2012, 07:24 -0600 schrieb Gary Thomas: On 2012-03-18 06:18, Martin Jansa wrote: On Sun, Mar 18, 2012 at 01:05:20PM +0100, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 16-03-12 20:41, Gary Thomas schreef: Signed-off-by: Gary Thomasg...@mlbassoc.com --- meta-oe/recipes-connectivity/midori/midori.inc |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/meta-oe/recipes-connectivity/midori/midori.inc b/meta-oe/recipes-connectivity/midori/midori.inc index 4c7147e..dccb3ee 100644 --- a/meta-oe/recipes-connectivity/midori/midori.inc +++ b/meta-oe/recipes-connectivity/midori/midori.inc @@ -1,4 +1,5 @@ DESCRIPTION = Midori is a lightweight web browser. +HOMEPAGE = http://www.twotoasts.de/index.php?/pages/midori_summary.html; LICENSE = LGPLv2.1 LIC_FILES_CHKSUM = file://COPYING;md5=fbc093901857fcd118f065f900982c24 Missing PR bump Khem applied it before my version upgrade, so it should be fine in feeds. Plus, it's informational only, so why bump the PR? Because the metadata is included in packages as far as I know. So package manager can display the homepage field. That's silly. Please use another wording next time. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH v2] v4l-utils: skip qv4l2 instead of using host toolchain
Dear Ciprian, thank you for your patch, but please adhere to the netiquette [1]. In particular please use interleaved quoting style. Am Mittwoch, den 22.02.2012, 15:21 +0200 schrieb Ciprian Ciubotariu: On Wed, 2012-02-22 at 09:42 +0100, Koen Kooi wrote: Op 22-02-12 01:05, Ciprian Ciubotariu schreef: See #2134 What does that mean? It's a reference to our internal issue tracker, which scans commit messages for such 'See #blah' references and makes a nice list of commits attached to each issue. I can strip that if needed. I was actually wondering how one can obey commit policies of more than one community, and still make use of git's DSCM abilities. Well you could provide more context so that it does not disturb the reader. Either appending »This issue is reported as ticket #2134 in the internal issue tracker of *your company name*.« or including it with more context in the commit message. Additionally more importantly your patch is missing the Signed-off-by line. Thanks, Paul [1] http://en.opensuse.org/openSUSE:Mailing_list_netiquette signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 1/3] proj: add recipe
Dear Jan,
thank you for your patch.
Am Dienstag, den 06.03.2012, 11:36 +0100 schrieb Jan Luebbe:
Could you please add the version number to the commit summary?
How did you test this package?
Signed-off-by: Jan Luebbe jlue...@debian.org
---
meta-oe/recipes-navigation/proj/proj.inc | 13 +
meta-oe/recipes-navigation/proj/proj_4.7.0.bb |7 +++
There seems to be 4.9 in OE-Classic? Is that not usable?
2 files changed, 20 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-navigation/proj/proj.inc
create mode 100644 meta-oe/recipes-navigation/proj/proj_4.7.0.bb
diff --git a/meta-oe/recipes-navigation/proj/proj.inc
b/meta-oe/recipes-navigation/proj/proj.inc
new file mode 100644
index 000..f6275d1
--- /dev/null
+++ b/meta-oe/recipes-navigation/proj/proj.inc
@@ -0,0 +1,13 @@
+DESCRIPTION = PROJ.4 - Cartographic Projections Library
+HOMEPAGE = http://trac.osgeo.org/proj/;
+SECTION = libs
+
+INC_PR = r0
+
+LICENSE = MIT
+LIC_FILES_CHKSUM = file://COPYING;md5=74d9aaec5fa0cd734341e8c4dc91b608
+
+SRC_URI = http://download.osgeo.org/proj/proj-${PV}.tar.gz;
+
+inherit autotools pkgconfig
+
Please no new line at the end.
diff --git a/meta-oe/recipes-navigation/proj/proj_4.7.0.bb
b/meta-oe/recipes-navigation/proj/proj_4.7.0.bb
new file mode 100644
index 000..8e4f901
--- /dev/null
+++ b/meta-oe/recipes-navigation/proj/proj_4.7.0.bb
@@ -0,0 +1,7 @@
+require proj.inc
+
+PR = ${INC_PR}.0
+
+SRC_URI[md5sum] = 927d34623b52e0209ba2bfcca18fe8cd
+SRC_URI[sha256sum] =
fc5440002a496532bfaf423c28bdfaf9e26cc96c84ccefcdefde911efbd98986
+
Please no new line at the end.
Also you do not need a INC file, because in OE-Core and meta-oe we try
to only have one version included.
Some of the comments also apply to your other patches.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH][meta-oe 1/1] numlockx: add 1.2
Dear Otavio,
Am Donnerstag, den 01.03.2012, 13:44 + schrieb Otavio Salvador:
your Signed-off-by line is missing.
---
meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb | 21
+
1 files changed, 21 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
diff --git a/meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
b/meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
new file mode 100644
index 000..0d4d9ff
--- /dev/null
+++ b/meta-oe/recipes-graphics/numlockx/numlockx_1.2.bb
@@ -0,0 +1,21 @@
+DESCRIPTION = Enable NumLock in X11 sessions
+HOMEPAGE = http://home.kde.org/~seli/numlockx/;
+SECTION = x11/apps
+DEPENDS = imake-native virtual/libx11 libxtst
That belongs after the license fields, does not it?
+LICENSE = MIT-X
+LIC_FILES_CHKSUM = file://LICENSE;md5=dcb1cc75e21540a4a66b54e38d95b047
+
+SRC_URI = http://home.kde.org/~seli/numlockx/numlockx-${PV}.tar.gz;
+
+SRC_URI[md5sum] = be9109370447eae23f6f3f8527bb1a67
+SRC_URI[sha256sum] =
e468eb9121c94c9089dc6a287eeb347e900ce04a14be37da29d7696cbce772e4
+
+inherit autotools
+
+EXTRA_OECONF = --x-includes=${STAGING_INCDIR} \
+--x-libraries=${STAGING_LIBDIR}
+
+do_configure_prepend() {
+# remove this from acinclude.m4 or build fails
+sed -i '/_AC_PATH_X_XMKMF/d' ${S}/acinclude.m4
+}
Otherwise with the above fixed this patch is
Reviewed-by: Paul Menzel paulepan...@users.sourceforge.net
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 1/1] nbench-byte: import recipe for oe-classic
Dear Chase,
thank you for your patch.
Am Dienstag, den 28.02.2012, 15:36 -0600 schrieb Chase Maupin:
Please add the version number to the commit summary.
Also s/for/from/.
nbench-byte: Add 2.2.3 (initial version)
* Import the nbench-byte recipe from the oe-classic git repo at
git://git.openembedded.org/openembedded commit id:
* 6fe7cef27069415f2eba36bc640cf59013d4979b
* Update LICENSE checksums
* Original Author:
* Marcin Juszkiewicz mar...@juszkiewicz.com.pl
* Modifications by:
* Koen Kooi k...@openembedded.org
* Martin Jansa martin.ja...@gmail.com
* Chris Larson chris_lar...@mentor.com
Information on how you tested it would be nice.
Signed-off-by: Chase Maupin chase.mau...@ti.com
---
.../nbench-byte/nbench-byte/nbench_32bits.patch| 46
.../nbench-byte/nbench-byte_2.2.3.bb | 26 +++
2 files changed, 72 insertions(+), 0 deletions(-)
create mode 100644
meta-oe/recipes-benchmark/nbench-byte/nbench-byte/nbench_32bits.patch
create mode 100644 meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb
diff --git
a/meta-oe/recipes-benchmark/nbench-byte/nbench-byte/nbench_32bits.patch
b/meta-oe/recipes-benchmark/nbench-byte/nbench-byte/nbench_32bits.patch
new file mode 100644
index 000..1b8a4dc
--- /dev/null
+++ b/meta-oe/recipes-benchmark/nbench-byte/nbench-byte/nbench_32bits.patch
@@ -0,0 +1,46 @@
+From 81f4043a6787060029ef20eed21cdcf3e50337df Mon Sep 17 00:00:00 2001
+From: Chase Maupin chase.mau...@ti.com
+Date: Tue, 28 Feb 2012 14:58:35 -0600
+Subject: [PATCH] nbench: modify Makefile for 32bit
+
+* Patch taken from OE classic git repository as of commit id
+ ad42bf9065928b2902d7d9534709d3ccea7ec956 and was added by:
+* Marcin Juszkiewicz mar...@juszkiewicz.com.pl
+* Notes from original patch were:
+
+BYTE Magazine's native benchmarks (also called BYTEmark) designed to
+expose the capabilities of a system's CPU, FPU and memory system.
+
+http://www.tux.org/~mayer/linux/
+
+Recipe from old Atmel overlay.
+
+Upstream-Status: Inappropriate [no upstream]
+
+Signed-off-by: Chase Maupin chase.mau...@ti.com
+---
+ Makefile |8 ++--
+ 1 files changed, 2 insertions(+), 6 deletions(-)
+
+diff --git a/Makefile b/Makefile
+index 5045c77..915866d 100644
+--- a/Makefile
b/Makefile
+@@ -119,12 +119,8 @@ emfloat.o: emfloat.h emfloat.c nmglobal.h pointer.h
Makefile
+ $(CC) $(MACHINE) $(DEFINES) $(CFLAGS)\
+ -c emfloat.c
+
+-pointer.h: pointer Makefile
+-$(CC) $(MACHINE) $(DEFINES) $(CFLAGS)\
+--o pointer pointer.c
+-rm -f pointer.h
+-if [ 4 = `./pointer` ] ; then touch pointer.h ;\
+-else echo #define LONG64 pointer.h ; fi
++pointer.h: Makefile
++touch pointer.h ;
+
+ misc.o: misc.h misc.c Makefile
+ $(CC) $(MACHINE) $(DEFINES) $(CFLAGS)\
+--
+1.7.0.4
+
diff --git a/meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb
b/meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb
new file mode 100644
index 000..9a002de
--- /dev/null
+++ b/meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb
@@ -0,0 +1,26 @@
+DESCRIPTION = BYTE Magazine's native benchmarks (also called BYTEmark) \
+designed to expose the capabilities of a system's CPU, FPU, \
+and memory system.
+HOMEPAGE = http://www.tux.org/~mayer/linux/;
+LICENSE = freely distributable
+LIC_FILES_CHKSUM =
file://README;beginline=57;endline=66;md5=020ef579f8fa5746b7e307a54707834f
+SECTION = console/utils
+
+SRC_URI = http://www.tux.org/~mayer/linux/${PN}-${PV}.tar.gz \
+ file://nbench_32bits.patch
+
+PR = r1
Please start with `r0` or to please Koen remove that line entirely.
+
+TARGET_CC_ARCH += ${CFLAGS} ${LDFLAGS}
+do_compile() {
+ oe_runmake
+}
+
+do_install () {
+ install -d ${D}${bindir}
+ install -m 0644 NNET.DAT ${D}${bindir}/
+ install -m 0755 nbench ${D}${bindir}/
+}
+
+SRC_URI[md5sum] = 285dfab361080759d477ea1fe7d3093a
+SRC_URI[sha256sum] =
723dd073f80e9969639eb577d2af4b540fc29716b6eafdac488d8f5aed9101ac
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe] vsftpd: add new package
Am Montag, den 20.02.2012, 14:51 +0100 schrieb Eric Bénard: - imported 2.0.5 from oe-classic - upgrade to 2.3.5 which is latest stable - tested on ARMv5 with Angstrom Please add the version number to the commit summary too. Signed-off-by: Eric Bénard e...@eukrea.com --- meta-oe/recipes-connectivity/vsftpd/files/init | 41 .../recipes-connectivity/vsftpd/files/vsftpd.conf | 108 .../vsftpd/vsftpd-2.3.5/makefile.patch | 47 + .../vsftpd/vsftpd-2.3.5/nopam.patch| 12 ++ .../recipes-connectivity/vsftpd/vsftpd_2.3.5.bb| 48 + 5 files changed, 256 insertions(+), 0 deletions(-) create mode 100755 meta-oe/recipes-connectivity/vsftpd/files/init create mode 100755 meta-oe/recipes-connectivity/vsftpd/files/vsftpd.conf create mode 100644 meta-oe/recipes-connectivity/vsftpd/vsftpd-2.3.5/makefile.patch create mode 100644 meta-oe/recipes-connectivity/vsftpd/vsftpd-2.3.5/nopam.patch create mode 100644 meta-oe/recipes-connectivity/vsftpd/vsftpd_2.3.5.bb […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] vlan: Port vlan 1.9 recipe from OE Classic
Dear Kelvin, Am Mittwoch, den 15.02.2012, 00:14 + schrieb Kelvin Lawson: please add the revision from the OE-Classic repository you took this from. Signed-off-by: Kelvin Lawson kelv...@users.sf.net --- meta-oe/recipes-connectivity/vlan/files/ip | 21 +++ .../recipes-connectivity/vlan/files/vlan-post-down | 28 + .../recipes-connectivity/vlan/files/vlan-pre-up| 61 meta-oe/recipes-connectivity/vlan/vlan_1.9.bb | 39 + 4 files changed, 149 insertions(+), 0 deletions(-) create mode 100644 meta-oe/recipes-connectivity/vlan/files/ip create mode 100644 meta-oe/recipes-connectivity/vlan/files/vlan-post-down create mode 100644 meta-oe/recipes-connectivity/vlan/files/vlan-pre-up create mode 100644 meta-oe/recipes-connectivity/vlan/vlan_1.9.bb diff --git a/meta-oe/recipes-connectivity/vlan/files/ip b/meta-oe/recipes-connectivity/vlan/files/ip new file mode 100644 index 000..d7de05c --- /dev/null +++ b/meta-oe/recipes-connectivity/vlan/files/ip @@ -0,0 +1,21 @@ +#!/bin/sh +# This should probably go into ifupdown +# But usually only those with lots of interfaces (vlans) need these +if [ -d /proc/sys/net/ipv4/conf/$IFACE ] +then + if [ -n $IF_IP_PROXY_ARP ]; then + if [ $IF_IP_PROXY_ARP -eq 1 ]; then + echo 1 /proc/sys/net/ipv4/conf/$IFACE/proxy_arp + else + echo 0 /proc/sys/net/ipv4/conf/$IFACE/proxy_arp + fi + fi + if [ -n $IF_IP_RP_FILTER ]; then + if [ $IF_IP_RP_FILTER -eq 0 ]; then + echo 0 /proc/sys/net/ipv4/conf/$IFACE/rp_filter + else + echo 1 /proc/sys/net/ipv4/conf/$IFACE/rp_filter + fi + fi +fi + diff --git a/meta-oe/recipes-connectivity/vlan/files/vlan-post-down b/meta-oe/recipes-connectivity/vlan/files/vlan-post-down new file mode 100644 index 000..89b16fb --- /dev/null +++ b/meta-oe/recipes-connectivity/vlan/files/vlan-post-down @@ -0,0 +1,28 @@ +#!/bin/sh + +# If IFACE is an automagic vlan interface (without the vlan-raw-device +# parameter) then let's try to discover the magic here.. Another way would be +# to just probe for the right device name in /proc/net/vlan + +case $IFACE in + # Ignore any alias (#272891) + *:*) +exit 0 + ;; + eth*.0*|bond*.0*|wlan*.0*) +IF_VLAN_RAW_DEVICE=`echo $IFACE|sed s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/` Your mailer corrupted the patch by adding automatic line breaks. + ;; + eth*.*|bond*.*|wlan*.*) +IF_VLAN_RAW_DEVICE=`echo $IFACE|sed s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/` + ;; + # Test for vlan raw device (#196890, #292648) + *) +[ -z $IF_VLAN_RAW_DEVICE ] exit 0 + ;; +esac + +if [ ! -x /sbin/vconfig ]; then +exit 0 +fi + +vconfig rem $IFACE diff --git a/meta-oe/recipes-connectivity/vlan/files/vlan-pre-up b/meta-oe/recipes-connectivity/vlan/files/vlan-pre-up new file mode 100644 index 000..b977be8 --- /dev/null +++ b/meta-oe/recipes-connectivity/vlan/files/vlan-pre-up @@ -0,0 +1,61 @@ +#!/bin/sh + +# Most of this stuff is to enable vlans + +case $IFACE in + # Ignore any alias (#272891) which uses interface:alabel + *:*) +exit 0 + ;; + vlan0*) +vconfig set_name_type VLAN_PLUS_VID +VLANID=`echo $IFACE|sed s/vlan0*//` + ;; + vlan*) +vconfig set_name_type VLAN_PLUS_VID_NO_PAD +VLANID=`echo $IFACE|sed s/vlan0*//` + ;; + eth*.0*|bond*.0*|wlan*.0*) +vconfig set_name_type DEV_PLUS_VID +VLANID=`echo $IFACE|sed s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//;s/wlan[0-9][0-9]*\.0*//` +IF_VLAN_RAW_DEVICE=`echo $IFACE|sed s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/` + ;; + eth*.*|bond*.*|wlan*.*) +vconfig set_name_type DEV_PLUS_VID_NO_PAD +VLANID=`echo $IFACE|sed s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g` +IF_VLAN_RAW_DEVICE=`echo $IFACE|sed s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/` + ;; + *.0*) +# Silently ignore interfaces which we do not (know how to) support +[ -z $IF_VLAN_RAW_DEVICE ] exit 0 +vconfig set_name_type DEV_PLUS_VID +VLANID=`echo $IFACE|sed s/[^.]*\.0*//g` + ;; + *.*) +# Silently ignore interfaces which we do not (know how to) support +[ -z $IF_VLAN_RAW_DEVICE ] exit 0 +vconfig set_name_type DEV_PLUS_VID_NO_PAD +VLANID=`echo $IFACE|sed s/[^.]*\.0*//g` + ;; + + *) +exit 0 + ;; +esac + +if [ -n $IF_VLAN_RAW_DEVICE ]; then +if [ ! -x /sbin/vconfig ]; then +exit 0 +fi +if ! ip link show dev $IF_VLAN_RAW_DEVICE /dev/null; then +echo $IF_VLAN_RAW_DEVICE does not exist, unable to create
Re: [oe] [meta-oe][PATCH] ntpclient: Port 2010_365 recipe from OE Classicntpclient: Port 2010_365 recipe from OE Classic.
Dear Kelvin,
thank you for the patch.
Am Mittwoch, den 15.02.2012, 00:34 + schrieb Kelvin Lawson:
You pasted the summary line twice. Also please add the ID to the commit
message.
* Also includes a Makefile fix to reorder the linker parameters.
Signed-off-by: Kelvin Lawson kelv...@users.sf.net
---
meta-oe/recipes-connectivity/ntpclient/files/init | 42 +
.../ntpclient/files/ntpclient-link.patch | 12 +
.../ntpclient/ntpclient_2010_365.bb| 47
3 files changed, 101 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-connectivity/ntpclient/files/init
create mode 100644
meta-oe/recipes-connectivity/ntpclient/files/ntpclient-link.patch
The patch is mangled.
create mode 100644
meta-oe/recipes-connectivity/ntpclient/ntpclient_2010_365.bb
diff --git a/meta-oe/recipes-connectivity/ntpclient/files/init
b/meta-oe/recipes-connectivity/ntpclient/files/init
new file mode 100644
index 000..7b85902
--- /dev/null
+++ b/meta-oe/recipes-connectivity/ntpclient/files/init
@@ -0,0 +1,42 @@
+#! /bin/sh
+#
+# This is an init script for openembedded
+# Copy it to /etc/init.d/ntpclient and type
+# update-rc.d ntpclient defaults 60
+#
+ntpclient=/sbin/ntpclient
+test -x $ntpclient || exit 0
+# Seconds Between Time Checks
+ntpinterval=600
+# Upstream NTP Server Name
+ntpserver=pool.ntp.org
+
+case $1 in
+ start)
+echo -n Starting NTP Client
+start-stop-daemon --start --quiet --background --make-pidfile
--pidfile /var/run/ntpclient.pid --exec $ntpclient -- -l -i
$ntpinterval -h $ntpserver
+echo .
+;;
+ stop)
+echo -n Stopping NTP Client
+start-stop-daemon --stop --quiet --pidfile /var/run/ntpclient.pid
+echo .
+;;
+ reload|force-reload)
+start-stop-daemon --stop --quiet --signal 1 --exec $ntpclient
+;;
+ restart)
+echo -n Stopping NTP Client
+start-stop-daemon --stop --quiet --pidfile /var/run/ntpclient.pid
+echo .
+sleep 1
+echo -n Starting NTP Client
+start-stop-daemon --start --quiet --background --make-pidfile
--pidfile /var/run/ntpclient.pid --exec $ntpclient -- -l -i
$ntpinterval -h $ntpserver
+echo .
+;;
+ *)
+echo Usage: /etc/init.d/ntpclient
{start|stop|reload|restart|force-reload}
+exit 1
+esac
+
+exit 0
diff --git a/meta-oe/recipes-connectivity/ntpclient/files/ntpclient-link.patch
b/meta-oe/recipes-connectivity/ntpclient/files/ntpclient-link.patch
new file mode 100644
index 000..b95fc24
--- /dev/null
+++ b/meta-oe/recipes-connectivity/ntpclient/files/ntpclient-link.patch
@@ -0,0 +1,12 @@
Please add a patch header as demanded in the commit and patch message
guide lines.
Also add what the error is please and describe the fix.
+diff -Naur ntpclient-2010/Makefile ntpclient-2010-patched/Makefile
+--- ntpclient-2010/Makefile 2010-12-28 06:26:36.0 +
ntpclient-2010-patched/Makefile 2012-01-31 00:55:36.0 +
+@@ -19,7 +19,7 @@
+ CFLAGS += -DENABLE_REPLAY
+ # CFLAGS += -DUSE_OBSOLETE_GETTIMEOFDAY
+
+-LDFLAGS += -lrt
++LDLIBS += -lrt
+
+ all: ntpclient
+
diff --git a/meta-oe/recipes-connectivity/ntpclient/ntpclient_2010_365.bb
b/meta-oe/recipes-connectivity/ntpclient/ntpclient_2010_365.bb
new file mode 100644
index 000..0ee7230
--- /dev/null
+++ b/meta-oe/recipes-connectivity/ntpclient/ntpclient_2010_365.bb
@@ -0,0 +1,47 @@
+DESCRIPTION = NTP (RFC-1305) client for unix-alike computers
+HOMEPAGE = http://doolittle.icarus.com/ntpclient;
That URL does not work for me. Please fix this up in a follow up patch.
+AUTHOR = Larry Doolittle la...@doolittle.boa.org
+RDEPENDS_${PN} = busybox
+SECTION = admin
+LICENSE = GPLv2
+LIC_FILES_CHKSUM =
file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6
+PR = r0
+# The ntpclient package uses version numbers that include an underscore :(
+PV = 2010_365
+# ntpclient unpacks into a directory that doesn't include version info :(
+S = ${WORKDIR}/${PN}-2010
+
+SRC_URI = http://doolittle.icarus.com/ntpclient/ntpclient_${PV}.tar.gz \
+ file://ntpclient-link.patch \
+ file://init \
+
+
+INITSCRIPT_NAME = ntpclient
+INITSCRIPT_PARAMS = defaults 65
+inherit update-rc.d
+
+LDFLAGS += -lrt
I guess your patch makes that obsolete?
+
+do_compile() {
+oe_runmake ntpclient
+oe_runmake adjtimex
+}
+
+do_install () {
+# Install the binary and tools
+install -D -m 0755 ${S}/ntpclient ${D}${base_sbindir}/ntpclient
+install -D -m 0755 ${S}/adjtimex ${D}${base_sbindir}/adjtimex.${PN}
+install -D -m 0755 ${S}/rate.awk ${D}${sbindir}/ntpclient-drift-rate.awk
+install -D -m 0755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/ntpclient
+}
+
+pkg_postinst_${PN} () {
+ update-alternatives --install ${base_sbindir}/adjtimex adjtimex
adjtimex.${PN} 100
+}
+
+pkg_prerm_${PN} () {
+
Re: [oe] Board support package (BSP) layers/distributions for Geode LX800
Dear Chris and OE folks, I am sorry for forwarding this message to the list that late. Am Mittwoch, den 01.02.2012, 08:14 + schrieb Chris Tapp: On 31 Jan 2012, at 15:15, Paul Menzel wrote: searching for a suited build configuration for a Geode LX800 based system I could only find the discussion about creating a BSP layer for it [1]. Was this layer created? I could not find it anywhere. Additionally could you give recommendations which build configuration is suited for a Geode system? Especially with OE-Core as the base. Did someone test the latest OE stuff with a Geode LX800 system recently? I've got a rough meta layer that I use with Yocto for the ALIX 3D3 (and similar). The aim (when I get a moment) is to make this in to a full BSP... I've got a modified kernel (linux-wrs 2.6.34.7) so that the ethernet, audio and Geode frame buffer are available and USB works. These are great news! Works fine with Poky 4. I had a quick go with 5, but I ended up with an image that failed to boot. I've not looked to find out why, but I don't expect it to be anything major. This isn't in a suitable state to push back (to Yocto), but I'm happy to share what I've got if it's going to be of any help. If you could publish your Git tree somewhere that would be great. Sorry for not sending this via the mailing list - the registered e- mail account is now just a forwarder and I can't get to the subscription page to change it as it's timing out. Please feel free to forward this to the list. Done now. I am sorry that this took so long. Thanks, Paul PS: Please keep Chris in CC and sorry Chris for sending this message twice. signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] systemd: move to v40 and don't kill user processes on exit
Am Dienstag, den 07.02.2012, 10:30 +0100 schrieb Koen Kooi:
This fixes screen and tmux persistency issues.
Two patches would have been better. Or is v40 also needed to fix these
issues?
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
---
.../0001-docs-fix-build-without-xsltproc.patch |8 ++--
...-logind-don-t-kill-user-processes-on-exit.patch | 31
meta-oe/recipes-core/systemd/systemd_git.bb|5 ++-
3 files changed, 38 insertions(+), 6 deletions(-)
create mode 100644
meta-oe/recipes-core/systemd/systemd/0002-systemd-logind-don-t-kill-user-processes-on-exit.patch
diff --git
a/meta-oe/recipes-core/systemd/systemd/0001-docs-fix-build-without-xsltproc.patch
b/meta-oe/recipes-core/systemd/systemd/0001-docs-fix-build-without-xsltproc.patch
index 6775349..390d65c 100644
---
a/meta-oe/recipes-core/systemd/systemd/0001-docs-fix-build-without-xsltproc.patch
+++
b/meta-oe/recipes-core/systemd/systemd/0001-docs-fix-build-without-xsltproc.patch
@@ -1,4 +1,4 @@
-From 97719ec99e3bd0040b616b044ab6ae33ae1cfd15 Mon Sep 17 00:00:00 2001
+From 7395173a5af08e9e58aed33e831d0bfc6515891d Mon Sep 17 00:00:00 2001
From: Koen Kooi k...@dominion.thruhere.net
Date: Sun, 2 Oct 2011 19:54:29 +0200
Subject: [PATCH 1/2] docs: fix build without xsltproc
@@ -6,18 +6,18 @@ Subject: [PATCH 1/2] docs: fix build without xsltproc
Make would choke on missing rules for man/systemd.1
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
Upstream-status: rejected [fix your docbook install]
+---
Makefile.am |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/Makefile.am b/Makefile.am
-index 110a2f4..a5e57b7 100644
+index f1f975f..53f99a1 100644
--- a/Makefile.am
+++ b/Makefile.am
-@@ -650,6 +650,7 @@ EXTRA_DIST += \
+@@ -649,6 +649,7 @@ EXTRA_DIST += \
src/acl-util.h \
src/logs-show.h
diff --git
a/meta-oe/recipes-core/systemd/systemd/0002-systemd-logind-don-t-kill-user-processes-on-exit.patch
b/meta-oe/recipes-core/systemd/systemd/0002-systemd-logind-don-t-kill-user-processes-on-exit.patch
new file mode 100644
index 000..c28f189
--- /dev/null
+++
b/meta-oe/recipes-core/systemd/systemd/0002-systemd-logind-don-t-kill-user-processes-on-exit.patch
@@ -0,0 +1,31 @@
+From eccbcfd37d41e1cb66bdf19cded899a36cc3842d Mon Sep 17 00:00:00 2001
+From: Koen Kooi k...@dominion.thruhere.net
+Date: Tue, 7 Feb 2012 10:12:51 +0100
+Subject: [PATCH 2/2] systemd-logind: don't kill user processes on exit
+
+This fixed screen and tmux
+
+Signed-off-by: Koen Kooi k...@dominion.thruhere.net
+
+Upstream-status: Unknown
+
+---
+ src/login/systemd-logind.conf |2 +-
+ 1 files changed, 1 insertions(+), 1 deletions(-)
+
+diff --git a/src/login/systemd-logind.conf b/src/login/systemd-logind.conf
+index 9909804..ba69b6c 100644
+--- a/src/login/systemd-logind.conf
b/src/login/systemd-logind.conf
+@@ -9,7 +9,7 @@
+
+ [Login]
+ #NAutoVTs=6
+-#KillUserProcesses=no
++KillUserProcesses=no
+ #KillOnlyUsers=
+ #KillExcludeUsers=root
+ #Controllers=
+--
+1.7.2.5
+
diff --git a/meta-oe/recipes-core/systemd/systemd_git.bb
b/meta-oe/recipes-core/systemd/systemd_git.bb
index 89f910b..c1a0117 100644
--- a/meta-oe/recipes-core/systemd/systemd_git.bb
+++ b/meta-oe/recipes-core/systemd/systemd_git.bb
@@ -14,14 +14,15 @@ inherit gitpkgv
PKGV = v${GITPKGVTAG}
PV = git
-PR = r13
+PR = r15
Only do `r14`?
inherit useradd pkgconfig autotools vala perlnative
-SRCREV = bbd9b8c2139a70005e4e83d198575e2a10fe1db2
+SRCREV = d26e4270409506cd398875216413b651d6ee7de6
SRC_URI = git://anongit.freedesktop.org/systemd/systemd;protocol=git \
file://0001-docs-fix-build-without-xsltproc.patch \
+
file://0002-systemd-logind-don-t-kill-user-processes-on-exit.patch \
${UCLIBCPATCHES} \
UCLIBCPATCHES =
I have no time to test this. But I guess you did.
Reviewed-by: Paul Menzel paulepan...@users.sourceforge.net
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH v2] tmux: Add initial recipe for vesion 1.6.
Am Donnerstag, den 02.02.2012, 20:22 +0100 schrieb Peter Tworek: From: Piotr Tworek ptwo...@opera.com Some configuration changed in your setup. Please try to avoid that so that so that changelog statistics can be more meaningful. There is the typo ve*r*sion in the summary. Run tested on netbook pro. Signed-off-by: Peter Tworek tworaz...@gmail.com Should you resend patches you can add the following. Acked-by: Paul Menzel paulepan...@users.sourceforge.net --- meta-oe/recipes-extended/tmux/tmux_1.6.bb | 18 ++ 1 files changed, 18 insertions(+), 0 deletions(-) create mode 100644 meta-oe/recipes-extended/tmux/tmux_1.6.bb […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Commit access for Peter Tworek
Dear OE developers, only OE-Classic can be pushed to and everything else is set up around a pull based model. Nevertheless Peter is quite active with sending patches and it would be nice if he could be promoted OpenEmbedded developer [1]. Sending this many patches Peter should probably set up some Git repository people can fetch from. I do not know if the OE infrastructure serves that purpose or not. To sum it up, I do not know if the New Dev procedure is still needed, but it would be nice to have something like that in the future. Thanks, Paul [1] http://www.openembedded.org/wiki/New_Dev signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] tmux: Add initial recipe for vesion 1.6.
Dear Peter,
thank you for your latest work. It is much appreciated.
Am Mittwoch, den 01.02.2012, 22:38 +0100 schrieb Peter Tworek:
This is just an optional request from me. I would like to see in the
commit message what build configuration you used for testing.
Signed-off-by: Peter Tworek tworaz...@gmail.com
---
meta-oe/recipes-extended/tmux/tmux_1.6.bb | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-extended/tmux/tmux_1.6.bb
diff --git a/meta-oe/recipes-extended/tmux/tmux_1.6.bb
b/meta-oe/recipes-extended/tmux/tmux_1.6.bb
new file mode 100644
index 000..eb6f7df
--- /dev/null
+++ b/meta-oe/recipes-extended/tmux/tmux_1.6.bb
@@ -0,0 +1,18 @@
+DESCRIPTION = Terminal multiplexer
+HOMEPAGE = http://tmux.sourceforge.net;
+SECTION = console/utils
+
+LICENSE = ISC
+LIC_FILES_CHKSUM =
file://tmux.c;startline=3;endline=17;md5=f36d9c9e6c1c24996a88891fdf783d04
+
+DEPENDS = ncurses libevent
+
+SRC_URI = ${SOURCEFORGE_MIRROR}/tmux/${P}.tar.gz
+SRC_URI[md5sum] = 3e37db24aa596bf108a0442a81c845b3
+SRC_URI[sha256sum] =
faee08ba1bd8c22537cd5b7458881d1bdb4985df88ed6bc5967c56881a7efbd6
+
+inherit autotools
+
+do_configure_prepend () {
+ sed -i -e 's:-I/usr/local/include::' Makefile.am || bb_fatal sed
failed
You can ensure that `sed` is available by depending on `sed-native` I
think. At least in OE-Classic this was available.
Additionally it would be great if you could contact upstream and make
them aware of this problem and maybe even provide a patch. So that in
the feature no adaptations are needed and other distributions/framework
can profit too.
+}
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-xfce][PATCH v2] Add recipe for xarchiver 0.5.2.
Dear Peter,
thank you for your patch.
Am Dienstag, den 31.01.2012, 20:54 +0100 schrieb Peter Tworek:
Please remember that the commit summary follows a certain pattern [1].
xarchiver: Add 0.5.2 (initial recipe)
Signed-off-by: Peter Tworek tworaz...@gmail.com
---
.../recipes-apps/xarchiver/xarchiver_0.5.2.bb | 16
1 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
diff --git a/meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
b/meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
new file mode 100644
index 000..66e9273
--- /dev/null
+++ b/meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
@@ -0,0 +1,16 @@
+DESCRIPTION = Lightweight, desktop independent GTK+ archive manager
+HOMEPAGE = http://xarchiver.sourceforge.net;
Does a »/« need to be added at the end?
+SECTION = x11
+
+LICENSE = GPLv2
Looking at the FAQ Xarchive is distributed under GPLv2+ [2].
+LIC_FILES_CHKSUM = file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f
+
+DEPENDS = gtk+ glib-2.0 xfce4-dev-tools-native
+
+SRC_URI = ${SOURCEFORGE_MIRROR}/${PN}/${P}.tar.bz2
+SRC_URI[md5sum] = 2bc7f06403cc6582dd4a8029ec9d038d
+SRC_URI[sha256sum] =
cea932ff9d505969201fd502470bbebbc5726ab3d6765e142fc8295aa677ad2a
+
+inherit gettext pkgconfig autotools gtk-icon-cache
+
+RRECOMMENDS_${PN} = lzop zip tar
With these changes this patch is
Acked-by: Paul Menzel paulepan...@users.sourceforge.net
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
[2] http://xarchiver.sourceforge.net/doc/ch01s03.html
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-xfce][PATCH v2] Add recipe for xarchiver 0.5.2.
Am Mittwoch, den 01.02.2012, 20:11 +0100 schrieb Peter Tworek:
On 02/01/2012 10:14 AM, Paul Menzel wrote:
Am Dienstag, den 31.01.2012, 20:54 +0100 schrieb Peter Tworek:
Please remember that the commit summary follows a certain pattern [1].
xarchiver: Add 0.5.2 (initial recipe)
Thanks for the tip, I didn't know about that.
Signed-off-by: Peter Tworektworaz...@gmail.com
---
.../recipes-apps/xarchiver/xarchiver_0.5.2.bb | 16
1 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
diff --git a/meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
b/meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
new file mode 100644
index 000..66e9273
--- /dev/null
+++ b/meta-xfce/recipes-apps/xarchiver/xarchiver_0.5.2.bb
@@ -0,0 +1,16 @@
+DESCRIPTION = Lightweight, desktop independent GTK+ archive manager
+HOMEPAGE = http://xarchiver.sourceforge.net;
Does a »/« need to be added at the end?
I'm not sure I follow. What do you mean by »/?
I am not sure if a slash is required for a valid URL.
HOMEPAGE = http://xarchiver.sourceforge.net/;
Please note the added slash / at the end.
+SECTION = x11
+
+LICENSE = GPLv2
Looking at the FAQ Xarchive is distributed under GPLv2+ [2].
I wasn't aware that GPLv2+ is a valid license value. Thanks I'll fix it
in v3.
+LIC_FILES_CHKSUM = file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f
+
+DEPENDS = gtk+ glib-2.0 xfce4-dev-tools-native
+
+SRC_URI = ${SOURCEFORGE_MIRROR}/${PN}/${P}.tar.bz2
+SRC_URI[md5sum] = 2bc7f06403cc6582dd4a8029ec9d038d
+SRC_URI[sha256sum] =
cea932ff9d505969201fd502470bbebbc5726ab3d6765e142fc8295aa677ad2a
+
+inherit gettext pkgconfig autotools gtk-icon-cache
+
+RRECOMMENDS_${PN} = lzop zip tar
With these changes this patch is
Acked-by: Paul Menzelpaulepan...@users.sourceforge.net
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
[2] http://xarchiver.sourceforge.net/doc/ch01s03.html
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Board support package (BSP) layers/distributions for Geode LX800
Dear OE folks, searching for a suited build configuration for a Geode LX800 based system I could only find the discussion about creating a BSP layer for it [1]. Was this layer created? I could not find it anywhere. Additionally could you give recommendations which build configuration is suited for a Geode system? Especially with OE-Core as the base. Did someone test the latest OE stuff with a Geode LX800 system recently? Thanks, Paul [1] https://lists.yoctoproject.org/pipermail/yocto/2010-November/002583.html signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] Fix typo in ctcs that causes build failure
Dear Philby, thank you for the patch. Am Donnerstag, den 05.01.2012, 18:23 +0530 schrieb philby john: From: Philby John pj...@mvista.com Date: Thu, 5 Jan 2012 18:01:11 +0530 Subject: [PATCH] Fix typo in ctcs that causes build failure Please adhere to the commit policy. Especially prefix the commit summary with the package name. RDEPENDS includes a line perl-module-tcntl, which is clearly a typo for perl-module-fcntl, without which you get a build failure. I see that this is an error and will push your improved patch. But I tried `bitbake -k ctcs` with `angstrom-2010.x` for `MACHINE = beagleboard` and it worked without problems. What command did you use to get a build error and how does it look like? I guess it is in the final image creation that the error occurs? Signed-off-by: Philby John pj...@mvista.com --- recipes/ctorrent/ctcs_1.4.1.bb |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) […] Thanks, Paul [1] http://www.openembedded.org/wiki/Commit_Policy signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] iw: use a newer commit in the public git
Dear Ayal,
Am Donnerstag, den 05.01.2012, 11:47 +0200 schrieb Eyal Reizer:
switch to use a newer commit in the public git
That line is redundant to the commit summary. Why not use the following
as the summary?
iw_git: Update to commit 8b2b1c6a (version 3.2)
Additionally please add if this just introduces new features or if it
fixes any problems for you.
And lastly please add how you have tested the new version.
Signed-off-by: Eyal Reizer ey...@ti.com
---
recipes/iw/iw_git.bb |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes/iw/iw_git.bb b/recipes/iw/iw_git.bb
index c98e1bc..f0dc7ff 100644
--- a/recipes/iw/iw_git.bb
+++ b/recipes/iw/iw_git.bb
@@ -4,9 +4,9 @@ SECTION = base
PRIORITY = optional
LICENSE = BSD
-SRCREV = 0a236ef5f8e4ba7218aac7d0cdacf45673d5b35c
-PR = r0
-PV = 0.9.22
+SRCREV = 8b2b1c6a77ee17e4128b22845cb8c5901de296c9
+PR = r1
+PV = 3.2
PR_append = +gitr${SRCPV}
I always forget, if a `PR` bump for a version update is needed if we
have `PR_append${SRCPV}`. Could you check that again, please.
DEPENDS = libnl pkgconfig
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCHv2] iw_git: Update to commit 8b2b1c6a (version 3.2)
Am Donnerstag, den 05.01.2012, 13:00 +0200 schrieb Eyal Reizer:
Upadte to the latest formal release of iw whcih has wowlan and p2p support.
Typos: Update, which. Spell checkers should find those without problems.
This version was tested together with official R4_SP2 nlcp release from TI
Using the following platfors:
am335x-evm, am180x-evm, am37x-evm
Signed-off-by: Eyal Reizer ey...@ti.com
---
recipes/iw/iw_git.bb |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes/iw/iw_git.bb b/recipes/iw/iw_git.bb
index c98e1bc..f0dc7ff 100644
--- a/recipes/iw/iw_git.bb
+++ b/recipes/iw/iw_git.bb
@@ -4,9 +4,9 @@ SECTION = base
PRIORITY = optional
LICENSE = BSD
-SRCREV = 0a236ef5f8e4ba7218aac7d0cdacf45673d5b35c
-PR = r0
-PV = 0.9.22
+SRCREV = 8b2b1c6a77ee17e4128b22845cb8c5901de296c9
+PR = r1
+PV = 3.2
PR_append = +gitr${SRCPV}
DEPENDS = libnl pkgconfig
Presuming the PR bump is needed:
Acked-by: Paul Menzel paulepan...@users.sourceforge.net
Does the rule still hold that only TI folks should push TI patches?
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCHv2][2011.03-maintenance] binutils_2.20.1 fixed md5 and sha256 sum
Dear Adriano, Am Samstag, den 31.12.2011, 15:25 +0100 schrieb Adriano Pallavicino: I can correctly download it from here ftp://ftp.gnu.org/gnu/binutils/binutils-2.20.1.tar.bz2 (as indicated inside bb file). The problem is only in sha256 and md5 sum. I'm using 2011.03-maintenance. I can desume that this branch is only for maintaining 2011.03 release. If someone decided to use binutils 2.20.1 why should I introduce the new 2.20.1a from master? All the things are tested with 2.20.1 and imho the branch 2011.03-maintenance must continue to utilize them. please read the commit messages and the included links in the commit messages for `binutils` in OpenEmbedded master branch. The link you posted is [1] is just a symlink to 2.20.1a [2]. Try it out with `wget`. The problem as mentioned in some commit messages was that some source files were not included in 2.20.1 and therefore upstream had to update that. Of course, if maintainers consider this patch useless, I'll remove it from here. Thanks, Paul [1] ftp://ftp.gnu.org/gnu/binutils/binutils-2.20.1.tar.bz2 [2] ftp://ftp.gnu.org/gnu/binutils/binutils-2.20.1a.tar.bz2 signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] ftplib: add initial version of recipe
Dear Vitaly,
thank you for your patch.
Am Sonntag, den 11.12.2011, 00:10 +0400 schrieb Vitaly Perov:
From: Vitaly Perov v...@vt-tech.eu
Please add the recipe version to the commit summary (subject) and follow
our commit policy [1][2][3].
Especially your Signed-off-by line is missing. Please also add
information how you tested that recipe.
---
recipes/ftplib/ftplib_3.1.bb | 38 ++
1 files changed, 38 insertions(+), 0 deletions(-)
create mode 100644 recipes/ftplib/ftplib_3.1.bb
diff --git a/recipes/ftplib/ftplib_3.1.bb b/recipes/ftplib/ftplib_3.1.bb
new file mode 100644
index 000..1dcdb3d
--- /dev/null
+++ b/recipes/ftplib/ftplib_3.1.bb
@@ -0,0 +1,38 @@
+#! /bin/sh
+
The shebang is not needed.
+DESCRIPTION = A set of routines that implement the FTP protocol
+HOMEPAGE = http://nbpfaus.net/~pfau/ftplib/;
+LICENSE = LGPLv2
+
+PR = r1
Please start with `r0` when submitting.
+
+##
Please remove these “style” lines. They are not common. [4]
+
+TARGET_CC_ARCH += ${LDFLAGS}
Why is that needed. Please add a comment and explain it in the commit
message.
+
+SRC_URI = http://nbpfaus.net/~pfau/ftplib/ftplib-${PV}-src.tar.gz;
Can you talk with upstream, that they release versioned tarballs
otherwise that will become a mess when upgraded.
+
+S = ${WORKDIR}/ftplib-${PV}
+
+##
+
+SRC_URI[md5sum] = c6af758ccbf806b28f022a587a41d9c5
+SRC_URI[sha256sum] =
be524e1086cfe9d86afa832e1413dde79a4e88ee8ea5325a87ffaaf6620a0a2b
+
+##
+do_compile() {
+cd linux make
Are you sure that works? At least `oe-runmake` should be used. This way
you should get not the correct target architecture since the build host
make is used. (I could be mistaken and maybe the Makefile figures it out
nevertheless.)
+}
+
+do_install() {
+install -d ${D}/${libdir}
+install -d ${D}/${includedir}
+install -d ${D}/${bindir}
+install -m 755 ${S}/linux/libftp.so.3.1 ${D}/${libdir}
+install -m 755 ${S}/linux/libftp.a ${D}/${libdir}
+install -m 644 ${S}/linux/ftplib.h ${D}/${includedir}
+install -m 755 ${S}/linux/qftp ${D}/${bindir}
+(cd ${D}/${libdir} \
+ ln -sf libftp.so.3.1 libftp.so.3 \
+ ln -sf libftp.so.3 libftp.so)
+}
I do not know if the last three lines are common. But if it works,
great!
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Category:Policy
[2] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
[3] http://www.openembedded.org/wiki/Commit_Policy
[4] http://www.openembedded.org/wiki/Styleguide
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [2011.03-maintenance] Pull request for libpam
Am Dienstag, den 06.12.2011, 15:40 + schrieb Mats Kärrman: From: openembedded-devel-boun...@lists.openembedded.org [openembedded-devel-boun...@lists.openembedded.org] on behalf of Paul Menzel [paulepan...@users.sourceforge.net] Sent: Tuesday, December 06, 2011 3:35 PM Am Dienstag, den 06.12.2011, 07:55 + schrieb Mats Kärrman: From: openembedded-devel-boun...@lists.openembedded.org [openembedded-devel-boun...@lists.openembedded.org] on behalf of Tom Rini [tom.r...@gmail.com] Sent: Monday, December 05, 2011 8:49 PM To: openembedded-devel@lists.openembedded.org Subject: Re: [oe] [2011.03-maintenance] Pull request for libpam On Mon, Dec 5, 2011 at 9:42 AM, Mats Kärrman mats.karr...@tritech.se wrote: Hello Tom, Please pull this commit from here: git://github.com/mkarrman/openembedded Branch: maintenance Mats Kärrman (1): 368c68a libpam_1.1.1: remove directory preventing /var/run from being volatile. Where is this a backport from? Thanks! My local project... Maybe I went ahead of myself but the solution is ~equivalent to the solution applied in libpam recipes of oe-core but 1.1.1 does not exist there and the corresponding fix was a part of the original recipes for later versions. so why not push it to OE-classic master first? Perhaps I missed the consensus of the Plans for OE classic future thread? To my understanding pull requests from somewhere and master will sooner-than-later die was the way to go. True. And a lot of developers answered they are still using OE-classic including master. So they would profit from your fix too. Also, pushing requires write access to the repo (that I don't have) but I can send a patch to the mailing list, if you like. I would push it for you. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] libpam_1.1.1: remove directory preventing /var/run from being volatile
Dear Mats,
thank you for sending the patch for OE-classic master.
Am Mittwoch, den 07.12.2011, 09:37 + schrieb Mats Kärrman:
The libpam make install creates a /var/run/sepermit folder that prevents
the later creation of a sym-link /var/run -- /var/volatile/run. This is
a problem because it causes additional wear to FLASH file systems.
The solution is ~equivalent to the solution applied in libpam recipes of
Does the ~ have any meaning or is it just a typo?
oe-core but v1.1.1 does not exist there and the corresponding fix was a
part of the original recipes for later versions.
Signed-off-by: Mats Kärrman mats.karr...@tritech.se
--
diff --git a/recipes/pam/files/05_libpam b/recipes/pam/files/05_libpam
new file mode 100644
index 000..5ae0c8e
--- /dev/null
+++ b/recipes/pam/files/05_libpam
@@ -0,0 +1,3 @@
+# Create sepermit folder in volatile fs
+d root root 0755 /var/run/sepermit none
+
In OE-core the file name is `99_pam` [1]. Why did the leading number
needed to be changed? Should that be also `05` in OE-core?
diff --git a/recipes/pam/libpam_1.1.1.bb b/recipes/pam/libpam_1.1.1.bb
index 09bc554..ba35d0c 100644
--- a/recipes/pam/libpam_1.1.1.bb
+++ b/recipes/pam/libpam_1.1.1.bb
@@ -15,7 +15,7 @@ DEPENDS = flex flex-native
# PAM is not a lot of use without configuration files and the plugins
RRECOMMENDS_${PN} = libpam-meta libpam-base-files
-PR = r2
+PR = r3
# The project is actually called Linux-PAM but that gives
# a bad OE package name because of the upper case characters
@@ -26,6 +26,7 @@ S = ${WORKDIR}/${p}
SRC_URI = ${KERNELORG_MIRROR}/pub/linux/libs/pam/library/${p}.tar.bz2 \
file://pam-nodocs.patch \
file://define-HAVE_DBM.patch \
+ file://05_libpam \
UCLIBC_PATCHES = file://Linux-PAM-1.1.0-uclibc.patch \
@@ -71,6 +72,17 @@ python populate_packages_prepend () {
packages.append(metapkg)
bb.data.setVar('PACKAGES', ' '.join(packages), d)
}
+
+do_install_append () {
+# Remove erroneously created /var/run dir
+rm -rf ${D}${localstatedir}/run
+
+# Install volatiles specification to make sure dir is created in run-time
+install -d ${D}${sysconfdir}/default
+install -d ${D}${sysconfdir}/default/volatiles
+install -m 0644 ${WORKDIR}/05_libpam
${D}${sysconfdir}/default/volatiles/
+}
+
SRC_URI[md5sum] = 9b3d952b173d5b9836cbc7e8de108bee
SRC_URI[sha256sum] =
608d3eb9d7a5e1a7505fff62e6a583fdb6e52dc05bf54dc9661c5f395
Thanks,
Paul
[1]
http://git.openembedded.org/openembedded-core/commit/meta/recipes-extended/pam/libpam/99_pam?id=698cef8322e5a5f18e50ce62f6c9d1f1f846677a
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe v4] add nostromo webserver
Dear Eric, Am Montag, den 05.12.2011, 10:07 +0100 schrieb Eric Bénard: Le 05/12/2011 08:25, Paul Menzel a écrit : Am Sonntag, den 04.12.2011, 21:30 +0100 schrieb Eric Bénard: this recipe was imported from OE-classic and upgraded to latest version could you add the version number to the commit summary? That would be great. Also the OE-classic commit SHA sum would be useful. useful for what ? an as precise as possible commit summary is useful especially when viewing commit logs with one line. in case someone wants details on this recipe in OE-classic he can simply do : cd recipes/nostromo git log and he gets all the details. You assume everybody has a checkout of OE-classic. And besides that it is required by the the (OE-core) guidelines [1]. Thanks, Paul [1] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [2011.03-maintenance] Pull request for libpam
Dear Mats, Am Dienstag, den 06.12.2011, 07:55 + schrieb Mats Kärrman: From: openembedded-devel-boun...@lists.openembedded.org [openembedded-devel-boun...@lists.openembedded.org] on behalf of Tom Rini [tom.r...@gmail.com] Sent: Monday, December 05, 2011 8:49 PM To: openembedded-devel@lists.openembedded.org Subject: Re: [oe] [2011.03-maintenance] Pull request for libpam On Mon, Dec 5, 2011 at 9:42 AM, Mats Kärrman mats.karr...@tritech.se wrote: Hello Tom, Please pull this commit from here: git://github.com/mkarrman/openembedded Branch: maintenance Mats Kärrman (1): 368c68a libpam_1.1.1: remove directory preventing /var/run from being volatile. Where is this a backport from? Thanks! My local project... Maybe I went ahead of myself but the solution is ~equivalent to the solution applied in libpam recipes of oe-core but 1.1.1 does not exist there and the corresponding fix was a part of the original recipes for later versions. so why not push it to OE-classic master first? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe v4] add nostromo webserver
Dear Eric, Am Sonntag, den 04.12.2011, 21:30 +0100 schrieb Eric Bénard: this recipe was imported from OE-classic and upgraded to latest version could you add the version number to the commit summary? That would be great. Also the OE-classic commit SHA sum would be useful. Signed-off-by: Eric Bénard e...@eukrea.com --- ...ile-add-possibility-to-override-variables.patch | 141 .../recipes-extended/nostromo/files/nhttpd.conf| 55 meta-oe/recipes-extended/nostromo/files/nostromo | 34 + meta-oe/recipes-extended/nostromo/files/volatiles |2 + .../recipes-extended/nostromo/nostromo_1.9.5.bb| 51 +++ 5 files changed, 283 insertions(+), 0 deletions(-) create mode 100644 meta-oe/recipes-extended/nostromo/files/0001-GNUmakefile-add-possibility-to-override-variables.patch create mode 100644 meta-oe/recipes-extended/nostromo/files/nhttpd.conf create mode 100644 meta-oe/recipes-extended/nostromo/files/nostromo create mode 100644 meta-oe/recipes-extended/nostromo/files/volatiles create mode 100644 meta-oe/recipes-extended/nostromo/nostromo_1.9.5.bb […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2] directvnc: Add initial recipe with version 0.7.7
Dear Rafael, thank you for your patch. Am Donnerstag, den 01.12.2011, 14:16 -0300 schrieb Rafael Ignacio Zurita: DirectVNC provides a very thin VNC client for unix framebuffer systems. I find it useful to add to the commit message what distribution and machine you tested the recipe with. Signed-off-by: Rafael Ignacio Zurita rafaelignacio.zur...@gmail.com --- Please add changes in the patch iteration (v2) below that line to help reviewers. recipes/directvnc/directvnc_0.7.7.bb | 13 + 1 files changed, 13 insertions(+), 0 deletions(-) create mode 100644 recipes/directvnc/directvnc_0.7.7.bb […] I pushed your patch to the repository as a4f35de0 [1]. Please also consider adding that recipe to meta-oe. The license checksum is used in OE classic but in meta-oe, so porting it should be just copying it to the right directory. Thanks a lot, Paul [1] http://git.openembedded.org/openembedded/commit/?id=a4f35de0f6ca17e92763d5a5f32422c56e5d8882 signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Documentation problems
Dear Rainer, thank you for sharing you view. Am Mittwoch, den 30.11.2011, 16:49 +0100 schrieb Rainer Koenig: Am 27.11.2011 03:40, schrieb Tom Rini: […] The things that make me amused is when I read comments like 8-snip And developers are not familiar with MediaWiki or most of the time hate it to not be able to use their favorite editor and to use a Web interface. 8-snip or 8-snip- Just having to edit a text file in an editor and commit this change is easier than working with a Web browser. 8-snip- Seriously guys, if you are a developer and you are able to understand the structure in OE and what bitbake does, then you should be able to understand the Wikimedia engine as well. »familiar« does not mean that they are not able to understand it. And if you want to avoid a web-editor then copy/paste the stuff to your favorite editor and do it there. Complaining about the tool you need to use sounds like a lame excuse for an software engineer. Of course, the Wikimedia engine offers advanced methods like categories to tag stuff but even that can be learned in short time. So I really doubt that the reason for not documenting is the Mediawiki engine. Unfortunately of lot of the responds miss the point. Instead of finding the reason why the reason for documentation is lacking it is discussed instead of WikiMedia is feasible or not although it has been there for a long time and it looks like it has failed. The point that documentation making has to be as easy as possible is agreed on by everyone. So please let us be constructive and share your comments in the sub thread »Re: [oe] [RFC] Documentation problems and future plans«. The other problem that I see when trying to contribute: This morning I registered my account rakoenig. Now, 7 hours later I'm still not able to edit anything and I have no idea how the process looks like to get write privileges. On the other hand, when I was doing the same in the Yocto wiki I was instantly able to write pages there. Tom King seems to have to acknowledge each registration. Please contact him about this. Now for the bugtracking thing. Yes, I think, that bugtracking is part of a project documentation and I would like to be able to find a bug and see a status. When you handle bugs on a mailing list I'm forced to use to search the archives for that bug and then I might find a thread that then has a lose end like --8-snip-- Will look again tomorrow. Go to bed. --8-snip-- That was the latest info on a bug when building samba and so far nobody knows if this bug is solved or not. If you hit the problem probably it has not been solved. Also you can search the commit log (`git log`) easily for changes in the Samba recipes. The funny thing is that when I first asked why you changed bug tracking to do it with a mailing list I was adivsed do search in the archives for that discussion. Searching the archives revealed that a lot of bugs hit Bugzilla and nobody took care of them. As Koen wrote. It was not used anymore and probably a bad thing to not shut down the Bugzilla instance immediately. So, from my external point of view the decision was Bugzilla is actually a mess, so lets try something else like the mailing list for bugtracking. See Koen’s response. The actual question is still how the developers feel. And as far as I know nobody has missed it. It looks like an email interface is a requisite for most of them. And hey, here we go... this thread is here because the wiki is out of date and we need to do...what? Switching to a new tool to confuse even more users? Or get the things done that need to be done? See above and the whole thread. And suggestions on how to get things done are very welcome. Just look at Yocto. From my point of view it looks much smarter because they have a bugtracker and post even statistics of their bugs which gives me the impression that their concern is improving qualitiy of their recipes. They have a good documentation that seems to get updated frequently, makes a good impression. They seem to have a roadmap for the future and do planned work. Compared to this OE (core) seems like a bunch of developers working on the bleeding edge of embedded Linux and don't document much because *they* understand what they are doing. Unfortunately a lot of (new) users don't understand it and would urgently need a good documentation. One difference is that Yocto is backed by corporations paying folks for documentation. And actually OE-core and Yocto should be pretty much aligned. Sorry for the maybe harsh words, but I really want to show you how OE looks to somebody approaching it. And of course I would like to help improving the docs, but for that OE needs a clear documentation policy and a process how to do and enforce that. I thought that was this topic of this thread the whole
Re: [oe] [PATCH] live555: add version 2011.11.20
Am Montag, den 28.11.2011, 09:49 +0100 schrieb Steffen Sledz:
Putting in here if and how you have tested this makes acknowledging
patches much easier!
Can the old recipe then removed? Could you also try to bring
`config.linux-cross` upstream, please?
Signed-off-by: Steffen Sledz sl...@dresearch-fe.de
---
recipes/live555/live555_2020.bb |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
create mode 100644 recipes/live555/live555_2020.bb
diff --git a/recipes/live555/live555_2020.bb
b/recipes/live555/live555_2020.bb
new file mode 100644
index 000..7256007
--- /dev/null
+++ b/recipes/live555/live555_2020.bb
@@ -0,0 +1,7 @@
+require live555.inc
+
+PR = ${INC_PR}.1
Please start with 0.
+
+SRC_URI[md5sum] = 8e5ebefdf7d12ca9cfd7175ff3d7eef2
+SRC_URI[sha256sum] =
695cf22d43516f082e26ee9eb8373a0ae3b4ed472f1e224b51d881219f694f2e
+
No new line at the end please. Git complains about that as white space
error too.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 1/2] gypsy: fix packaging
Am Donnerstag, den 24.11.2011, 15:47 +0100 schrieb Steffen Sledz:
A wrong path had avoided the packaging of the dbus starter script
/usr/share/dbus-1/system-services/org.freedesktop.Gypsy.service.
So why not use
gypsy: fix packaging of DBus starter script
as the commit summary?
Signed-off-by: Steffen Sledz sl...@dresearch-fe.de
---
recipes/gypsy/gypsy.inc|4 +++-
recipes/gypsy/gypsy_0.7.bb |2 ++
2 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/recipes/gypsy/gypsy.inc b/recipes/gypsy/gypsy.inc
index eab062c..964e336 100644
--- a/recipes/gypsy/gypsy.inc
+++ b/recipes/gypsy/gypsy.inc
@@ -3,6 +3,8 @@ LICENSE = GPL
SECTION = x11
DEPENDS = glib-2.0 dbus-glib bluez4 libxslt-native
+INC_PR = r1
+
inherit autotools pkgconfig
do_configure_prepend () {
@@ -14,6 +16,6 @@ PACKAGES += libgypsy libgypsy-dev libgypsy-dbg
FILES_lib${PN} = ${libdir}/lib*.so*
FILES_lib${PN}-dev = ${includedir}/* ${libdir}/*.la ${libdir}/*.a
${libdir}/pkgconfig
FILES_lib${PN}-dbg = ${libdir}/.debug
-FILES_${PN} = ${datadir}/dbus-1/services/ ${libexecdir}/gypsy-daemon
${sysconfdir}/dbus-1/system.d/*
+FILES_${PN} = ${datadir}/dbus-1/system-services/*
${libexecdir}/gypsy-daemon ${sysconfdir}/dbus-1/system.d/*
FILES_${PN}-dbg =${libexecdir}/.debug*
CONFFILES_${PN} = ${sysconfdir}/dbus-1/system.d/Gypsy.conf
diff --git a/recipes/gypsy/gypsy_0.7.bb b/recipes/gypsy/gypsy_0.7.bb
index 8cd8760..a10cd6e 100644
--- a/recipes/gypsy/gypsy_0.7.bb
+++ b/recipes/gypsy/gypsy_0.7.bb
@@ -1,5 +1,7 @@
require gypsy.inc
+PR = ${INC_PR}.1
+
Since `INC_PR` is increased, `${INC_PR}.0` should be fine.
SRC_URI = http://gypsy.freedesktop.org/releases/gypsy-0.7.tar.gz;name=gypsy
\
file://docs-reference-am.patch \
file://remove-werror.patch \
With the changes above this recipe is
Acked-by: Paul Menzel paulepan...@users.sourceforge.net
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] live555: add version 2011.11.20
Am Montag, den 28.11.2011, 10:10 +0100 schrieb Paul Menzel:
Am Montag, den 28.11.2011, 09:49 +0100 schrieb Steffen Sledz:
Putting in here if and how you have tested this makes acknowledging
patches much easier!
It does not even fetch for me anymore.
ERROR: Function 'Fetch failed: Unable to fetch URL
http://www.live555.com/liveMedia/public/live.2011.11.20.tar.gz from any
source.' failed
Can the old recipe then removed? Could you also try to bring
`config.linux-cross` upstream, please?
Signed-off-by: Steffen Sledz sl...@dresearch-fe.de
---
recipes/live555/live555_2020.bb |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
create mode 100644 recipes/live555/live555_2020.bb
diff --git a/recipes/live555/live555_2020.bb
b/recipes/live555/live555_2020.bb
new file mode 100644
index 000..7256007
--- /dev/null
+++ b/recipes/live555/live555_2020.bb
@@ -0,0 +1,7 @@
+require live555.inc
+
+PR = ${INC_PR}.1
Please start with 0.
+
+SRC_URI[md5sum] = 8e5ebefdf7d12ca9cfd7175ff3d7eef2
+SRC_URI[sha256sum] =
695cf22d43516f082e26ee9eb8373a0ae3b4ed472f1e224b51d881219f694f2e
+
No new line at the end please. Git complains about that as white space
error too.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [RFC] Documentation problems and future plans
Dear everyone, Am Samstag, den 26.11.2011, 19:40 -0700 schrieb Tom Rini: As things stand today, the wiki is out of date and a number of folks refuse to work on it. Using things like It's all text! for firefox only go so far and don't solve problems like people just avoiding documentation anyhow. the Special Pages page [1] has interesting information. For example you can get an overview of the recent changes in the Wiki [2]. Paul Menzel has mentioned that ikiwiki has been mentioned before and that lets us have the website in a repository. Do folks have other ideas? Before the implementation is discussed, could we decide what documentation we need and what is possible to maintain in the long run? Avoiding maintenance and duplicate efforts should be the objective. 1. User manual 2. FAQ 3. README 4. Guidelines (Commit, patch, style) 5. Getting started document (could be included in 1.) 6. Git usage (a lot of existing documentation for that one elsewhere) or can be put in a file `HACKING`. 7. … Formatted in a markup language like Markdown those could be converted to HTML easily. The second question is, is OE-core documented in the OE wiki or for example at the Yocto project? To get users started we could also recommend to use the Ȧngström scripts or to take a look at the Yocto project, i. e. just point to distributions being well documented. They have a Wiki already [3] and we could decide to use that instead. Or we could say to use use the Wiki at eLinux.org [4]. Thanks, Paul [1] http://www.openembedded.org/wiki/Special:SpecialPages [2] http://www.openembedded.org/wiki/Special:RecentChanges [3] https://wiki.yoctoproject.org/wiki/Main_Page [4] http://elinux.org/Main_Page signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Documentation problems
Am Sonntag, den 27.11.2011, 17:06 + schrieb Paul Eggleton: On Sunday 27 November 2011 17:58:00 Frans Meulenbroeks wrote: What is the problem with being it a wiki (probably with authorized users to avoid spam). I'd say let everyone who wants to contribute. If someone makes a mistake it can easily be corrected and/or reverted, and if someone messes things up on purpose and/or creates more bad than good such a (non)contributor can be banned. Disadvantage of a pull model is: - more difficult to make changes (e.g. if I see a typo in a wiki and I have write permission, I'll fix it; however if it invokes checking out a file, make the edit, commit it, mail a pull request, most likely I'll decide it is not worth the effort - more administrative workload (that is probably better spent on actually doing things). - It sends out a message of distrust. Not really a good way to create involvement. One might feel that it improves quality; then again also in a wiki one can review and improve (or revert) changes. As far as I see it we are all adults (at least I think so) all interested in improving OE so no unnecessary barriers should be raised. Frans. PS: it is quite possible to backup a wiki (and I hope this is done at regular intervals with our wiki). Also all edits are recorded so they can always be tracked back and (if needed) undone. I agree with all of this. We shouldn't be putting more barriers up to contributing to the documentation - there are already enough. Only Koen brought up the idea of the pull model. By itself, ikiwiki also allows Web edits [1]. Additionally, you have not addressed the point that reality shows, that not a lot of people write documentation and use it. The best way to “enforce” this is to add documentation with the corresponding change. Thanks, Paul [1] http://ikiwiki.info/ (just click on edit) signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Documentation problems
Am Sonntag, den 27.11.2011, 18:56 + schrieb Paul Eggleton: On Sunday 27 November 2011 19:38:39 Paul Menzel wrote: Only Koen brought up the idea of the pull model. By itself, ikiwiki also allows Web edits [1]. Yes but what benefit do we get by changing the system? Only that the backend changes to git? Given that MediaWiki is familiar to many (thanks to Wikipedia) I would be hesitant to replace it with anything less widely understood. Everything is in one place. And developers are not familiar with MediaWiki or most of the time hate it to not be able to use their favorite editor and to use a Web interface. Maybe a survey should be held. It is work in the beginning but would pay back in the end since this infrastructure should be used for a while. Or we just try it out. Additionally, you have not addressed the point that reality shows, that not a lot of people write documentation and use it. The best way to “enforce” this is to add documentation with the corresponding change. I'm not sure I understand what you mean here. If you're suggesting that we will be able to force people to write changes for the documentation together with their changes to the code, I think there are two problems with this: (1) it assumes that we already have complete documentation for the current state of the code; Then people could update that part in one go or should at least add a TODO somewhere. (2) given that writing meaningful commit messages is a challenge for many contributors, you're going to have a very difficult time getting people to write documentation for their changes as well. That is our choice to make. Either we want good documentation. Then we have to make this a requirement and contributors have to deal with that but will get help from the list too. Or we do not enforce this and probably the documentation will be lacking. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Documentation problems
Am Sonntag, den 27.11.2011, 22:49 +0100 schrieb Frans Meulenbroeks: Generally speaking writing documentation is difficult and a task not liked by most sw developers (me included). People should be encouraged and it should be as easy as possible. The more difficult it is, the less likely it is people will do it. My point exactly! Just having to edit a text file in an editor and commit this change is easier than working with a Web browser. Then again I am not too sure what we need, given the yocto documentation. See the other sub thread. BTW and if a certain part of the wiki is for a specific purpose (e.g. related to a distro): in most wiki's it is possible to restrict access to certain pages to a specific group. Sure. But has this been necessary in the past? Then again that all needs to be managed True. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Plans for OE classic future
Am Samstag, den 26.11.2011, 16:45 +0100 schrieb Frans Meulenbroeks: […] (and more general: oe classic still has quite some recipes that are not in oe-core or meta-oe (apart from the fact that the latter is not really too open to contributions; see the email thread on id3lib from a while ago). No, that is not true. The id3lib recipe had formal issues so it could not be applied [2]. The only issue is that there is a disagreement if the guidelines for OE-core [2] are mandatory for meta-oe too. Thanks, Paul [1] http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-October/035854.html [2] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Plans for OE classic future
Am Samstag, den 26.11.2011, 14:36 -0700 schrieb Tom Rini: On Sat, Nov 26, 2011 at 8:49 AM, Frans Meulenbroeks wrote: 2011/11/26 Tom Rini On Sat, Nov 26, 2011 at 3:57 AM, Ulf Samuelsson wrote: On 2011-11-25 23:04, Tom Rini wrote: On Fri, Nov 25, 2011 at 12:31 AM, Frans Meulenbroeks wrote: After all, isn't one of the purposes of OE to promote information sharing, cooperation and the use of openembedded technology (and not make things harder). One of the points of making master read-only would be to ensure that changes aren't lost. Perhaps the transition needs to be: - master is as it is today - master becomes oe-core backport || master-only bugfixes only - master becomes read only. And we go from the first step to the second step sometime sooner rather than later. The top of my head date would be before the paid-developers go on end of year breaks to try and make sure all the hobbyist folks start their hacking with oe-core+etc rather than master and risk getting caught later. I'm open to arguments on why that's exactly backwards... Won't it be a problem for existing projects, if you cannot add fixes to cope with new host OS versions. At the moment, openembedded-classic does not build properly with Ubuntu 11.10 . Won't what be a problem? Either oe-core+meta-oe+etc fails on 11.10 (so, fix it there first then backport changes) or it's fine and you can either find the relevant changes there and move them or it's a oe.dev-only bug and just needs to be fixed, under my proposal (until we reach the point where everyone is OK calling it r/o). And part of this is to say that yes, existing projects external to oe.dev need to move to oe-core(+meta-oe+whatever else) (where layers should be making their life easier or again, there's problems we're unaware of and need to be made aware of) or explain why they can't ever move (and are forking the project?). See the message on NIOS that I just posted. Addressed there :) Also I am not opposed to making oe classic master the place where patches may land before they end up in the maintenance thread, but I am strongly opposed to making OE classic read only on short notice (which as suggested by Koen earlier). I believe master needs to go read-only, or at least backport||master-only-problems bugfix only, sooner rather than later. The arguments seem to be: - Some people or projects use master and can't move * So don't move, but do expect to need to either migrate to 2011.03-maintenance or carry more fixes locally. This is still not understandable. I understand that you want developers to move to OE-core and meta-oe. But trying to force people by making master read-only is the wrong way. It just arbitrarily puts a burden on current users. You can advertise prominently that OE-core and meta-oe should be used. Over the time people will move and a lot of people have expressed their willingness to move in the future. With my 2011.03-maintenance hat on, if someone says for my project to move I need N patches moved from master to maintenance, I'm fine reviewing that pull request. I thought that was always possible in the past. - There's concern that $something won't be able to work with oe-core+meta-oe+etc * These are problems that either need to be fixed or assumptions that aren't correct. - Lack of recipes in meta-oe * The recipes people need have been moved, stuff that isn't can be when someone needs it. id3lib was mentioned as an example of why there might be problems getting things moved to meta-oe. I can't help but notice it's also been moved into meta-oe. As Bernhard noted in this reply. OE-Core and meta-oe seriously lack documentation. And if it is just that our Wiki currently is still based on OE-classic. And in my experience not a lot of people put effort behind it and just neglect it. (New users will search for tutorials and help on the WWW and there currently a lot is dealing with OE-classic.) Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Plans for OE classic future
Am Samstag, den 26.11.2011, 15:33 -0700 schrieb Tom Rini: On Sat, Nov 26, 2011 at 3:01 PM, Paul Menzel wrote: Am Samstag, den 26.11.2011, 14:36 -0700 schrieb Tom Rini: On Sat, Nov 26, 2011 at 8:49 AM, Frans Meulenbroeks wrote: 2011/11/26 Tom Rini On Sat, Nov 26, 2011 at 3:57 AM, Ulf Samuelsson wrote: On 2011-11-25 23:04, Tom Rini wrote: On Fri, Nov 25, 2011 at 12:31 AM, Frans Meulenbroeks wrote: After all, isn't one of the purposes of OE to promote information sharing, cooperation and the use of openembedded technology (and not make things harder). One of the points of making master read-only would be to ensure that changes aren't lost. Perhaps the transition needs to be: - master is as it is today - master becomes oe-core backport || master-only bugfixes only - master becomes read only. And we go from the first step to the second step sometime sooner rather than later. The top of my head date would be before the paid-developers go on end of year breaks to try and make sure all the hobbyist folks start their hacking with oe-core+etc rather than master and risk getting caught later. I'm open to arguments on why that's exactly backwards... Won't it be a problem for existing projects, if you cannot add fixes to cope with new host OS versions. At the moment, openembedded-classic does not build properly with Ubuntu 11.10 . Won't what be a problem? Either oe-core+meta-oe+etc fails on 11.10 (so, fix it there first then backport changes) or it's fine and you can either find the relevant changes there and move them or it's a oe.dev-only bug and just needs to be fixed, under my proposal (until we reach the point where everyone is OK calling it r/o). And part of this is to say that yes, existing projects external to oe.dev need to move to oe-core(+meta-oe+whatever else) (where layers should be making their life easier or again, there's problems we're unaware of and need to be made aware of) or explain why they can't ever move (and are forking the project?). See the message on NIOS that I just posted. Addressed there :) Also I am not opposed to making oe classic master the place where patches may land before they end up in the maintenance thread, but I am strongly opposed to making OE classic read only on short notice (which as suggested by Koen earlier). I believe master needs to go read-only, or at least backport||master-only-problems bugfix only, sooner rather than later. The arguments seem to be: - Some people or projects use master and can't move * So don't move, but do expect to need to either migrate to 2011.03-maintenance or carry more fixes locally. This is still not understandable. I understand that you want developers to move to OE-core and meta-oe. But trying to force people by making master read-only is the wrong way. It just arbitrarily puts a burden on current users. You can advertise prominently that OE-core and meta-oe should be used. Over the time people will move and a lot of people have expressed their willingness to move in the future. Well, on this side of the fence I think we're unclear what more needs to be said. Like Frans and Bernhard wrote, for new users a README on OE-classic would be nice and the Wiki needs to be updated. Maybe also a deprecation notice when pulling from the master branch. For old users as also written no further comments are needed. They are experienced enough and have heard your arguments. Now you should let them make their own decisions even if you do not like it. In my mind, we couldn't do a technical branching of the repository, we made a new one. But people are still working off of a branch made against an 8 month old snapshot. We really want to encourage this to stop. If we were all in one repository still, it would be people saying don't make legacy/main read-only! I still want to add things to it!. I did not understand that paragraph. Sorry. With my 2011.03-maintenance hat on, if someone says for my project to move I need N patches moved from master to maintenance, I'm fine reviewing that pull request. I thought that was always possible in the past. It always has been, but since there's been confusion apparently about what can and cannot happen with the branch today, I want to spell it out. I would be very happy to review whatever changes need to come in from master that would make $project be able to say OK, I can use the maintenance branch until we have the time to move to oe-core/etc. - There's concern that $something won't be able to work with oe-core+meta-oe+etc * These are problems that either need to be fixed or assumptions that aren't correct. - Lack of recipes in meta-oe * The recipes people need have been moved, stuff that isn't can be when someone
Re: [oe] Plans for OE classic future
Am Donnerstag, den 24.11.2011, 09:12 -0200 schrieb Otavio Salvador: On Thu, Nov 24, 2011 at 08:23, Hauser, Wolfgang (external) wrote: I would vote for an open classic master for bugfixing too, our project based on 2011.03-maintenance goes into the final phase and to switch to oe-core, the budged is not available jet. I also believe oe-classic master ought to be read-only as soon as possible; I understand that people are using it but the soonner we make it read-only, sooner people will move to oe-core otherwise people will keep starting new project on it and it will never die. You seem to use OE-core and meta-oe already so I understand your point of view. Martin, Koen, Andreas and you are doing the major work for meta-oe and not a lot of other people contribute. In my opinion it is a bad sign to force people to switch. OE-core and meta-oe should be so appealing that they switch by themselves. My impression from reading the list and from IRC is that a lot of people still have objections and are not totally comfortable. Good community management would be to listen to these people then try to find solutions and implement them. People then should come by themselves. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2] batctl: Add version 2011.3.0 (initial recipe)
Dear Todd,
thank you for the follow up.
Am Montag, den 14.11.2011, 09:17 -0600 schrieb Todd Kempel:
* batmand is included in the current OE repository but is not being actively
maintained.
The batman-adv kernel module is a replacement for batmand and requires
batctl for operation.
Is batmand still useful? If yes, could you do a clean up?
Recipe has been tested and binary found fully operational using Angstrom on
gumstix board.
Signed-off-by: Todd Kempel todd.kem...@gmail.com
---
recipes/batctl/batctl.inc | 20
recipes/batctl/batctl_2011.3.0.bb |6 ++
2 files changed, 26 insertions(+), 0 deletions(-)
create mode 100644 recipes/batctl/batctl.inc
create mode 100644 recipes/batctl/batctl_2011.3.0.bb
diff --git a/recipes/batctl/batctl.inc b/recipes/batctl/batctl.inc
new file mode 100644
index 000..75bb62f
--- /dev/null
+++ b/recipes/batctl/batctl.inc
@@ -0,0 +1,20 @@
+DESCRIPTION = Control application for B.A.T.M.A.N. routing protocol kernel
module for multi-hop ad-hoc mesh networks.
+HOMEPAGE = http://www.open-mesh.net/;
+SECTION = console/network
+PRIORITY = optional
+LICENSE = GPL
I corrected the license field.
/*
* Copyright (C) 2007-2011 B.A.T.M.A.N. contributors:
*
* Andreas Langer an.lan...@gmx.de, Marek Lindner lindner_ma...@yahoo.de
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of version 2 of the GNU General Public
* License as published by the Free Software Foundation.
*
* This program is distributed in the hope that it will be useful, but
* WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
* 02110-1301, USA
*
*/
+
+INC_PR = r0
+
+RDEPENDS_${PN} = kernel-module-batman-adv
+
+SRC_URI =
http://downloads.open-mesh.net/batman/stable/sources/batctl/batctl-${PV}.tar.gz;
+
+do_compile() {
+ oe_runmake
+}
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 batctl ${D}${bindir}
+}
diff --git a/recipes/batctl/batctl_2011.3.0.bb
b/recipes/batctl/batctl_2011.3.0.bb
new file mode 100644
index 000..97d8e17
--- /dev/null
+++ b/recipes/batctl/batctl_2011.3.0.bb
@@ -0,0 +1,6 @@
+require batctl.inc
+PR = ${INC_PR}.0
+
+
+SRC_URI[md5sum] = 8eb197896049bb04a6beef56015a16b6
+SRC_URI[sha256sum] =
94922fd167d2bca5193cc7465bfc212c2c3595da70e653506493dfc65e4410fb
I pushed this as ee6171ae [1]. Could you please update the state in the
patch queue [2].
Otherwise please note that OE-core and meta-oe get the most development
today. It would be great if you could also submit your recipe for
inclusion in meta-oe.
Thanks,
Paul
[1]
http://git.openembedded.org/openembedded/commit/?id=ee6171aee5f69f079bf87dd143f80899bddd6755
[2] http://www.openembedded.org/wiki/Patchwork
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-xfce 2/5] midori: update to 0.4.2
Am Sonntag, den 13.11.2011, 22:22 +0100 schrieb Andreas Müller: for bad and sometimes vala-dirty people [1] we keep overwriting of waf since midori still installs waf 1.5.19 (checked by bitbake -cunpack midori midori-workdir/waf --version). [1] http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-November/035995.html# Please enter the commit message for your changes. Lines starting Some template line got in the commit message. Signed-off-by: Andreas Müller schnitzelt...@gmx.de Reviewed-by: Paul Menzel paulepan...@users.sourceforge.net […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] RFC: Clean up omap3.inc
Am Donnerstag, den 10.11.2011, 14:55 -0700 schrieb Tom Rini: On Thu, Nov 10, 2011 at 1:54 PM, Florian Boor wrote: Am 10.11.2011 21:27, schrieb Koen Kooi: Wrong. You can do the following in your machine.conf: require omap3.inc EXTRA_IMAGEDEPENDS = whatever this is a workaround for a bad misconception. EXTRA_IMAGEDEPENDS could have been appended everywhere and this intrusive override might break quite a lot. In OE classic, no. In meta-ti the cleanup is already underway. I do not care bout meta-ti, its is broken in OE classic. Removing this hardcoded dependency would not break anything. Only the board maintainers who want to get it built automatically would have to add it. But, that's most of them today. Sorry Tom, could you try harder to explain the reason, please? How many boards are there in the upstream OE repository depending on this and would have to be changed? I think Florian could commit that with his clean up easily. On the other side developers opposing this clean up could at least offer to add a comment to the file with a proposed work around for people hitting this issue. Still there should be a good reason. Like all your internal TI projects depend on this for example. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] commiting recipe for batctl
Dear Todd,
thank you for your contribution.
Am Freitag, den 11.11.2011, 15:17 -0600 schrieb Todd Kempel:
From: Todd Kempel todd@todd-VirtualBox.(none)
Please use a real email address.
git config user.email todd.kem...@gmail.com
The commit summary should be the following
batctl: Add version 2011.3.0 (initial recipe)
Please also add a short description how you tested this recipe and if
everything works. Did you also try a uClibc based build?
There are some guide lines in the OE wiki [1][2][3].
Signed-off-by: Todd Kempel todd@todd-VirtualBox.(none)
---
recipes/batctl/batctl-2011.3.0/makefile-fix.patch | 18 +
recipes/batctl/batctl.inc | 28
+
recipes/batctl/batctl_2011.3.0.bb |6
recipes/batctl/files/makefile-fix.patch | 18 +
4 files changed, 70 insertions(+), 0 deletions(-)
create mode 100644 recipes/batctl/batctl-2011.3.0/makefile-fix.patch
create mode 100644 recipes/batctl/batctl.inc
create mode 100644 recipes/batctl/batctl_2011.3.0.bb
create mode 100644 recipes/batctl/files/makefile-fix.patch
diff --git a/recipes/batctl/batctl-2011.3.0/makefile-fix.patch
b/recipes/batctl/batctl-2011.3.0/makefile-fix.patch
new file mode 100644
index 000..45bd69e
--- /dev/null
+++ b/recipes/batctl/batctl-2011.3.0/makefile-fix.patch
Please add a patch header [3]. Like what problem does that patch fix and
did you send it upstream?
@@ -0,0 +1,18 @@
+--- batctl-2011.3.0.orig/Makefile2011-11-09 16:22:58.088166320 -0600
batctl-2011.3.0/Makefile 2011-11-09 16:33:21.181006028 -0600
+@@ -24,7 +24,6 @@
+ MANPAGE = man/batctl.8
+
+ # batctl flags and options
+-CFLAGS += -pedantic -Wall -W -std=gnu99 -fno-strict-aliasing -MD
Why does not that work? Do you have an idea?
+ LDLIBS += -lm
+
+ # disable verbose output
+@@ -38,7 +37,6 @@
+ endif
+
+ # standard build tools
+-CC ?= gcc
Does `oe_runmake` not overwrite that?
+ RM ?= rm -f
+ INSTALL ?= install
+ MKDIR ?= mkdir -p
diff --git a/recipes/batctl/batctl.inc b/recipes/batctl/batctl.inc
new file mode 100644
index 000..71dd948
--- /dev/null
+++ b/recipes/batctl/batctl.inc
@@ -0,0 +1,28 @@
+DESCRIPTION = Routing protocol daemon for multi-hop ad-hoc mesh networks.
+SECTION = console/network
+PRIORITY = optional
+LICENSE = GPL
+HOMEPAGE = http://www.open-mesh.net/;
`HOMEPAGE` goes below the description please [4].
+
+INC_PR = r2
Start with `r0` please when committing it upstream.
+
+RDEPENDS_${PN} = kernel-module-tun
+
+SRC_URI =
http://downloads.open-mesh.net/batman/stable/sources/batctl/batctl-${PV}.tar.gz
\
+ file://makefile-fix.patch \
+
+
+S = ${WORKDIR}/batctl-${PV}
That should be the default?
+
+do_compile() {
+ oe_runmake
+}
+
+do_stage() {
+ :
+}
`do_stage` is deprecated [5].
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 batctl ${D}${bindir}
+}
diff --git a/recipes/batctl/batctl_2011.3.0.bb
b/recipes/batctl/batctl_2011.3.0.bb
new file mode 100644
index 000..2b32e63
--- /dev/null
+++ b/recipes/batctl/batctl_2011.3.0.bb
@@ -0,0 +1,6 @@
+require batctl.inc
+PR = ${INC_PR}.1
Start with `.0` please.
+
+
+SRC_URI[md5sum] = 8eb197896049bb04a6beef56015a16b6
+SRC_URI[sha256sum] =
94922fd167d2bca5193cc7465bfc212c2c3595da70e653506493dfc65e4410fb
diff --git a/recipes/batctl/files/makefile-fix.patch
b/recipes/batctl/files/makefile-fix.patch
new file mode 100644
index 000..45bd69e
--- /dev/null
+++ b/recipes/batctl/files/makefile-fix.patch
@@ -0,0 +1,18 @@
+--- batctl-2011.3.0.orig/Makefile2011-11-09 16:22:58.088166320 -0600
batctl-2011.3.0/Makefile 2011-11-09 16:33:21.181006028 -0600
+@@ -24,7 +24,6 @@
+ MANPAGE = man/batctl.8
+
+ # batctl flags and options
+-CFLAGS += -pedantic -Wall -W -std=gnu99 -fno-strict-aliasing -MD
+ LDLIBS += -lm
+
+ # disable verbose output
+@@ -38,7 +37,6 @@
+ endif
+
+ # standard build tools
+-CC ?= gcc
+ RM ?= rm -f
+ INSTALL ?= install
+ MKDIR ?= mkdir -p
This is already in the correct folder. Please commit just one patch. ;-)
Otherwise that looks nice. Please resubmit as `[PATCH v2]` [6].
--subject-prefix=PATCH v2
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Policy
[2] http://www.openembedded.org/wiki/Commit_log_example
[3] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
[4] http://www.openembedded.org/wiki/Styleguide
[5] http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] SRC_URI = svn://svn.o-hand.com/repos/matchbox/trunk
Am Donnerstag, den 10.11.2011, 16:11 -0600 schrieb David Thomas:
I have tried every possible way, 8 hours so far, to get this file to
process these patches. I got the patches, I have set up local
repositories, ad nasium and same response, unable to fetch from any
source.
I have tired every combination, I have tried every possible link, url,
SRC_URI = git:///home/twoods/local;protocol=file;branch=master
git://git.yoctoproject.org/matchbox-keyboard;protocol=git;file://smallscreen-fontsize.patch;patch=1
and on and on. Every single project I have seen references the same
SRC_URI = svn://svn.o-hand.com/repos/matchbox/trunk;module=${PN};proto=http \
I am at the point of hurling this machine out a window. How could this
be so cryptic and difficult?
Does anyone have a idea?
DESCRIPTION = Matchbox virtual keyboard for X11
LICENSE = GPL
DEPENDS = libfakekey expat libxft
RCONFLICTS = matchbox-keyboard-inputmethod
RPROVIDES_${PN} = matchbox-keyboard-inputmethod
SECTION = x11
PV = 0.0+svnr${SRCPV}
PR =r7
SRC_URI = https://git.gitorious.org/cm-t3530/cm-t3530.git;protocol=git \
file://smallscreen-fontsize.patch;patch=1 \
file://2-Add-new-modifier--layout--Used-to-cycle-thru-all-available-layouts.patch;patch=1
\
Please turn off line wrapping.
file://3-Changes-to-improve-layout-rendering--especially-after-adding-support-for.patch;patch=1
\
file://4-Add-rendering-debug-logging.patch;patch=1 \
file://5-Add-support-for-loading-multiple-independent-layouts.patch;patch=1
\
file://6-Add-layout-switch-key-to-all-layouts.patch;patch=1 \
Where do you have these files stored?
S = ${WORKDIR}/${PN}
inherit autotools pkgconfig gettext
EXTRA_OECONF = --disable-cairo
FILES_${PN} = ${bindir}/* \
${datadir}/applications \
${datadir}/pixmaps \
${datadir}/matchbox-keyboard
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] SRC_URI = svn://svn.o-hand.com/repos/matchbox/trunk
Am Donnerstag, den 10.11.2011, 21:17 -0600 schrieb David Thomas:
On Nov 10, 2011, at 5:04 PM, Paul Menzel wrote:
Am Donnerstag, den 10.11.2011, 16:11 -0600 schrieb David Thomas:
I have tried every possible way, 8 hours so far, to get this file to
process these patches. I got the patches, I have set up local
repositories, ad nasium and same response, unable to fetch from any
source.
I have tired every combination, I have tried every possible link, url,
SRC_URI = git:///home/twoods/local;protocol=file;branch=master
git://git.yoctoproject.org/matchbox-keyboard;protocol=git;file://smallscreen-fontsize.patch;patch=1
and on and on. Every single project I have seen references the same
SRC_URI =
svn://svn.o-hand.com/repos/matchbox/trunk;module=${PN};proto=http \
I am at the point of hurling this machine out a window. How could this
be so cryptic and difficult?
Does anyone have a idea?
DESCRIPTION = Matchbox virtual keyboard for X11
LICENSE = GPL
DEPENDS = libfakekey expat libxft
RCONFLICTS = matchbox-keyboard-inputmethod
RPROVIDES_${PN} = matchbox-keyboard-inputmethod
SECTION = x11
PV = 0.0+svnr${SRCPV}
PR =r7
SRC_URI = https://git.gitorious.org/cm-t3530/cm-t3530.git;protocol=git \
file://smallscreen-fontsize.patch;patch=1 \
file://2-Add-new-modifier--layout--Used-to-cycle-thru-all-available-layouts.patch;patch=1\
file://3-Changes-to-improve-layout-rendering--especially-after-adding-support-for.patch;patch=1
\
file://4-Add-rendering-debug-logging.patch;patch=1 \
file://5-Add-support-for-loading-multiple-independent-layouts.patch;patch=1
\
file://6-Add-layout-switch-key-to-all-layouts.patch;patch=1 \
Where do you have these files stored?
$OEBASE/sources or /home/twoods/sources
You have to put them in the recipe folder under `files`, which is
deprecated, or cm-t3530-… like here.
recipes/vdr$ ls -r
vdr.inc
vdr_1.7.16.bb
vdr-1.7.16:
0003-uclibc-Add-lintl-to-LIBS.patch 0001-Makefile-Pass-LDFLAGS.patch
0002-tools.h-include-stdarg.h.patch
This is even in the manual I think and you have plenty of examples in
the repository already.
[…]
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] OpenEmbedded General Assembly, 28 October 2011, Prague, CZ
Dear Jeff, Am Freitag, den 04.11.2011, 10:28 -0700 schrieb Jeff Osier-Mixon: OpenEmbedded General Assembly, 28 November 2011, 6pm-9pm CET I am guessing you meant October? Clarion Congress Hotel, Prague, CZ Proceedings taken by Jeff Osier-Mixon, apologies for any misspellings _ […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] [meta-oe] slim fails to install with unmet dependency of `libpam-meta`
Dear OE folks, using the systemd demo image [1] based on OE-core and meta-oe and running `opkg update` and `opkg install slim` an error was displayed that the dependency for libpam-meta could not be installed. Thanks, Paul [1] http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-systemd-image-eglibc-ipk-v2011.11-core-beagleboard.rootfs.tar.bz2 signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH 1/1] dhcp: add system support to dhcp-server
Dear Otavio, thank you for the patch. system*d* in the commit summary. Am Montag, den 07.11.2011, 14:33 + schrieb Otavio Salvador: Signed-off-by: Otavio Salvador ota...@ossystems.com.br --- .../recipes-connectivity/dhcp/dhcp_4.2.0.bbappend | 19 +++ .../recipes-connectivity/dhcp/files/dhcpd.service | 12 2 files changed, 31 insertions(+), 0 deletions(-) create mode 100644 meta-oe/recipes-connectivity/dhcp/dhcp_4.2.0.bbappend create mode 100644 meta-oe/recipes-connectivity/dhcp/files/dhcpd.service […] diff --git a/meta-oe/recipes-connectivity/dhcp/files/dhcpd.service b/meta-oe/recipes-connectivity/dhcp/files/dhcpd.service new file mode 100644 index 000..70beee9 --- /dev/null +++ b/meta-oe/recipes-connectivity/dhcp/files/dhcpd.service @@ -0,0 +1,12 @@ +[Unit] +Description=Dynamic Host Configuration Protocol (DHCP) +After=syslog.target network.target + +[Service] +Type=forking +PIDFile=/var/run/dhcpd.pid +EnvironmentFile=-/etc/default/dhcp-server +ExecStart=/usr/sbin/dhcpd -cf /etc/dhcp/dhcpd.conf -q $INTERFACES + +[Install] +WantedBy=multi-user.target Did you write this yourself or did you get it from somewhere? Is upstream aware of this? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Insanity
Dear David, Am Mittwoch, den 02.11.2011, 08:53 -0500 schrieb David Thomas: I am new to OE and trying to get this tool chain working has about finished me off. After struggling with distro issues for 2 weeks I installed Ubuntu 10... and now the tools at least seem to work. I am using a OMAP board from Compulabs and the stable kernel they offer on their website. This is for a hi-rel application. However after gating all this way I am now stopped at HANDHELDS_CVS=cvs://anoncvs:anon...@cvs.handhelds.org/cvs as it appears this is no longer available? update.rc seems to be the hangup. Does it really need to be this difficult? I am at the point of tossing in the towel and moving in to some other platform. There are no mirrors? This is a nightmare and as usual, no solutions seem to be available. I am sorry, but you do not provide any useful information at all and the subject is not helpful either. Ȧngström should have mirrors and normally just following the build instruction’s from the Ȧngström Web site [1] is all you have to do. Thanks, Paul [1] http://www.angstrom-distribution.org/building-angstrom signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] guilt-native: changed SRC_URI
Dear Neil,
Am Dienstag, den 01.11.2011, 09:46 -0700 schrieb nmac...@gmail.com:
From: Neil MacMunn n...@gumstix.com
* the old kernel.org URI is no longer reachable
… because of the server compromise.
Signed-off-by: Neil MacMunn n...@gumstix.com
---
meta/recipes-devtools/guilt/guilt-native_0.33.bb |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-devtools/guilt/guilt-native_0.33.bb
b/meta/recipes-devtools/guilt/guilt-native_0.33.bb
index 54b1b90..325118a 100644
--- a/meta/recipes-devtools/guilt/guilt-native_0.33.bb
+++ b/meta/recipes-devtools/guilt/guilt-native_0.33.bb
@@ -8,7 +8,7 @@ PR = r1
inherit native
-SRC_URI =
${KERNELORG_MIRROR}/linux/kernel/people/jsipek/guilt/guilt-${PV}.tar.gz\
+SRC_URI =
http://ftp.sunet.se/pub/Linux/kernels/people/jsipek/guilt/guilt-${PV}.tar.gz\
If I understand that correctly, you should define `KERNELORG_MIRROR` to
something else in your `local.conf` until kernel.org is back hosting
these archives. Otherwise all mirrors need to be changed. Maybe this
variable could be also redefined to some other mirror and later we will
revert that commit when kernel.org is back up.
file://guilt-push.patch \
file://guilt-pop.patch \
file://guilt.patch \
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl][meta-oe 05/12] id3lib: Import from openembedded classic
Am Montag, den 31.10.2011, 09:55 + schrieb Paul Eggleton: On Saturday 29 October 2011 13:33:27 Paul Menzel wrote: +LIC_FILES_CHKSUM = files://COPYING;md5=3bf50002aefd002f49e7bb854063f7e7 +PR = r0 According to Koen these are going away. Well, Koen might reject PR = r0 in meta-oe, that's fine; however LIC_FILES_CHKSUM is mandatory or the recipe will not build, and I don't think that will be changing any time soon. I have considered if it would be desirable/possible to eliminate it for recipes that don't install any files (e.g. tasks), so far I haven't done any work on that. For normal recipes it is required however. I meant »this is« instead of »these are«. (Or did I mean these occurrences of `PR`.)I am sorry for the confusion. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl][meta-oe 05/12] id3lib: Import from openembedded classic
Am Montag, den 31.10.2011, 11:50 +0100 schrieb Koen Kooi: Op 29-10-11 14:33, Paul Menzel schreef: Dear Martin, dear Denis, Am Samstag, den 29.10.2011, 12:29 +0200 schrieb Martin Jansa: From: Denis 'GNUtoo' Carikli gnu...@no-log.org Added LIC_FILES_CHKSUM, and fixed LICENSE Signed-off-by: Denis 'GNUtoo' Carikli gnu...@no-log.org Signed-off-by: Martin Jansa martin.ja...@gmail.com NACK. please add the version you import and the commit ID you import from. This is all written in the guide lines [1]! And as I've said before, meta-oe is not oe-dev, so you can't use take the old 'rules' and apply them to meta-oe 1:1! The guide lines I referred to [1] have been written for OE-core. ;-) Thanks, Paul [1] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] bluez4_4.95.bb: new recipe for building bluez-4.95
Dear Vita,
are you reading the list or do I have to add your address to the CC
field?
Am Sonntag, den 30.10.2011, 10:58 +0100 schrieb Preskovsky, Vita:
Please see my answers bellow.
thank you for your answer.
-Original Message-
Sent: Tuesday, October 11, 2011 4:32 PM
Subject: Re: [oe] [PATCH] bluez4_4.95.bb: new recipe for building bluez-4.95
Dear Vita,
thank you for your patch.
Am Dienstag, den 11.10.2011, 11:08 +0200 schrieb Vita Preskovsky:
Using
bluez4: Add version 4.95
as the commit summary would be cleaner. Use `git commit --amend` to change
that.
Additionally you should elaborate more in the commit message what the patch
is doing.
1. Have you tested it? Is it just an upgrade because of or does version
4.91 in the repository have any short comings so that it should be removed?
I tested this recipe, and the reason I added this version is that we want to
use this version of Bluez in our release.
I guess you tested it using Ȧngström, so the old recipe can be removed.
Please note that oe-core already has version 4.96.
Signed-off-by: Vita Preskovsky vi...@ti.com
---
recipes/bluez/bluez4_4.95.bb | 30 ++
1 files changed, 30 insertions(+), 0 deletions(-) create mode 100644
recipes/bluez/bluez4_4.95.bb
diff --git a/recipes/bluez/bluez4_4.95.bb
b/recipes/bluez/bluez4_4.95.bb new file mode 100644 index
000..a682d6a
--- /dev/null
+++ b/recipes/bluez/bluez4_4.95.bb
@@ -0,0 +1,30 @@
+require bluez4.inc
+SRC_URI = \
+ http://www.kernel.org/pub/linux/bluetooth/bluez-${PV}.tar.gz \
2. As far as I know kernel.org after the compromise presently does not
provide that archive. So the recipe will not build unless there is a mirror
somewhere. Do you know of a mirror?
There are two possible locations for this package:
http://www.mirrorservice.org/sites/ftp.kernel.org/pub/linux/bluetooth/bluez-4.95.tar.gz
http://www.angstrom-distribution.org/unstable/sources/bluez-4.95.tar.gz
I changed the SRC_URI in my working directory for the first location and it
worked fine. So with what location do you prefer the recipe will be released?
I am unsure about the policy myself and I do not think an “OE mirror”
has that particular archive.
+ file://bluetooth.conf \
+
+
+SRC_URI[md5sum] = 341294b2849a04a4afff5c96bfbf30b2
+SRC_URI[sha256sum] =
d6ea9de410fc2bcd2620d709c2202893b218e2e6a55c3c0ce6bebd27fa4120f6
+
+DEFAULT_PREFERENCE = -1
3. Why?
+DEFAULT_PREFERENCE_angstrom = 1
4. Have you talked to the Ȧngström maintainers?
These two variables are defined in the previous version of bluez4 recipe:
bluez4_4.89.bb. Without these two definitions in my recipe bitbake prefers
the old recipe upon mine, which doesn't leave me a choice but to define these
variables.
The “correct” way would be to first add that recipe and then afterward
sent a patch to change the preferences which the Ȧngström maintainers
have to acknowledge.
+
+DEPENDS += libsndfile1
+
+PR = ${INC_PR}.0
+
+# Not all distros have a recent enough udev BTUDEV =
+--disable-udevrules
+BTUDEV_angstrom = --enable-udevrules
+BTUDEV_shr = --enable-udevrules
+
+EXTRA_OECONF += ${BTUDEV}
+do_configure_append(){
+ echo #define LIBUDEV_I_KNOW_THE_API_IS_SUBJECT_TO_CHANGE
+${S}/config.h }
+
+FILES_${PN}-dbg += \
+ ${base_libdir}/udev/.debug \
+ ${libdir}/*/.debug \
+
Otherwise this recipe looks good. Is it planned for branch
2011.03-maintenance?
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl][meta-oe 08/12] elsa: add new login manager for Enlightenment
Dear Martin,
could you add the version in the commit summary?
Am Samstag, den 29.10.2011, 12:29 +0200 schrieb Martin Jansa:
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
meta-efl/recipes-efl/efl/elsa_svn.bb | 16
1 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 meta-efl/recipes-efl/efl/elsa_svn.bb
diff --git a/meta-efl/recipes-efl/efl/elsa_svn.bb
b/meta-efl/recipes-efl/efl/elsa_svn.bb
new file mode 100644
index 000..59127d3
--- /dev/null
+++ b/meta-efl/recipes-efl/efl/elsa_svn.bb
@@ -0,0 +1,16 @@
+DESCRIPTION = Login manager for Enlightenment
+DEPENDS = efreet eina eet ecore elementary
+LICENSE = GPLv3+
+LIC_FILES_CHKSUM = file://COPYING;md5=d32239bcb673463ab874e80d47fae504
+SECTION = e/apps
+
+inherit e gettext
+SRC_URI = ${E_SVN}/trunk/PROTO;module=${SRCNAME};proto=http;scmdata=keep
+S = ${WORKDIR}/${SRCNAME}
+
+EXTRA_OECONF = --with-edje-cc=${STAGING_BINDIR_NATIVE}/edje_cc
+
+PV = 0.0.4+svnr${SRCPV}
+SRCREV = ${EFL_SRCREV}
+
+#RDEPENDS_${PN} = ${PN}-themes
Is there a reason the last line is commented out(?)?
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl][meta-oe 09/12] task-x11-server: import from Angstrom
Dear Martin,
Am Samstag, den 29.10.2011, 12:29 +0200 schrieb Martin Jansa:
* from meta-angstrom revision 8aa9581a920abae8878df2f3faf9857474edd1f8
I am not knowledgeable about the new infrastructure, so I cannot comment
on the import.
* added RPROVIDES to be able to drop server part from task-x11
* updated DESCRIPTION to match
* renamed to task-x11-server for upgradeable path
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
meta-oe/recipes-core/tasks/task-x11-server_1.0.bb | 24
+
1 files changed, 24 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-core/tasks/task-x11-server_1.0.bb
diff --git a/meta-oe/recipes-core/tasks/task-x11-server_1.0.bb
b/meta-oe/recipes-core/tasks/task-x11-server_1.0.bb
new file mode 100644
index 000..86de1ec
--- /dev/null
+++ b/meta-oe/recipes-core/tasks/task-x11-server_1.0.bb
@@ -0,0 +1,24 @@
+DESCRIPTION = Task for a image with Xserver
s/a image/an image/
+LICENSE = MIT
+LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
+PR = r9
+
+inherit task
+
+# for backwards compatibility
+RPROVIDES_${PN} = task-x11-server
+
+XSERVER ?= xserver-xorg \
+ xf86-input-evdev \
+ xf86-input-mouse \
+ xf86-video-fbdev \
+ xf86-input-keyboard \
+
+
+
+RDEPENDS_${PN} = \
+ ${XSERVER} \
+
+
+PACKAGE_ARCH = ${MACHINE_ARCH}
+
No newline needed at the end?
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl][meta-oe 12/12] elfe: add another patch to fix API changes
Dear Martin,
Am Samstag, den 29.10.2011, 12:29 +0200 schrieb Martin Jansa:
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
...update-again-to-even-newer-elementary-API.patch | 105
meta-efl/recipes-efl/e17/elfe_svn.bb |2 +
2 files changed, 107 insertions(+), 0 deletions(-)
create mode 100644
meta-efl/recipes-efl/e17/elfe/0001-elfe-update-again-to-even-newer-elementary-API.patch
diff --git
a/meta-efl/recipes-efl/e17/elfe/0001-elfe-update-again-to-even-newer-elementary-API.patch
b/meta-efl/recipes-efl/e17/elfe/0001-elfe-update-again-to-even-newer-elementary-API.patch
new file mode 100644
index 000..ad1c259
--- /dev/null
+++
b/meta-efl/recipes-efl/e17/elfe/0001-elfe-update-again-to-even-newer-elementary-API.patch
[…]
diff --git a/meta-efl/recipes-efl/e17/elfe_svn.bb
b/meta-efl/recipes-efl/e17/elfe_svn.bb
index 151ef7e..5b703dc 100644
--- a/meta-efl/recipes-efl/e17/elfe_svn.bb
+++ b/meta-efl/recipes-efl/e17/elfe_svn.bb
@@ -5,4 +5,6 @@ PR = ${INC_PR}.1
require e-module.inc
+SRC_URI += file://0001-elfe-update-again-to-even-newer-elementary-API.patch
+
DEPENDS += elementary
is `PR = ${INC_PR}.2` needed? Or does the package content not change?
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl][meta-oe 05/12] id3lib: Import from openembedded classic
Dear Martin, dear Denis,
Am Samstag, den 29.10.2011, 12:29 +0200 schrieb Martin Jansa:
From: Denis 'GNUtoo' Carikli gnu...@no-log.org
Added LIC_FILES_CHKSUM, and fixed LICENSE
Signed-off-by: Denis 'GNUtoo' Carikli gnu...@no-log.org
Signed-off-by: Martin Jansa martin.ja...@gmail.com
NACK.
please add the version you import and the commit ID you import from.
This is all written in the guide lines [1]!
---
meta-oe/recipes-multimedia/id3lib/id3lib_3.8.3.bb | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-multimedia/id3lib/id3lib_3.8.3.bb
diff --git a/meta-oe/recipes-multimedia/id3lib/id3lib_3.8.3.bb
b/meta-oe/recipes-multimedia/id3lib/id3lib_3.8.3.bb
new file mode 100644
index 000..9be4ffb
--- /dev/null
+++ b/meta-oe/recipes-multimedia/id3lib/id3lib_3.8.3.bb
@@ -0,0 +1,18 @@
+DESCRIPTION = Library for interacting with ID3 tags.
+SECTION = libs/multimedia
+PRIORITY = optional
+DEPENDS = zlib
+LICENSE = GPLv2+
That is not correct [2], it is `LGPLv2+`. Additionally the header
ordering is not the standard. I thought migration to meta-oe was
supposed to be a chance to clean up the recipes.
+LIC_FILES_CHKSUM = files://COPYING;md5=3bf50002aefd002f49e7bb854063f7e7
+PR = r0
According to Koen these are going away. Unfortunately these things are
discussed on oe-core instead of openembedded-devel as described in the
Wiki [3].
+inherit autotools
+
+SRC_URI = ${SOURCEFORGE_MIRROR}/id3lib/id3lib-${PV}.tar.gz;name=archive \
+
http://ftp.de.debian.org/debian/pool/main/i/id3lib3.8.3/id3lib3.8.3_3.8.3-7.2.diff.gz;name=patch
\
+
+
+SRC_URI[archive.md5sum] = 19f27ddd2dda4b2d26a559a4f0f402a7
+SRC_URI[archive.sha256sum] =
2749cc3c0cd7280b299518b1ddf5a5bcfe2d1100614519b68702230e26c7d079
+SRC_URI[patch.md5sum] = 805c0320a2efb21c40ce06fa13cd7c4b
+SRC_URI[patch.sha256sum] =
9f03b59ccc8826a5be55a3dcde2f889067d58bdc72bf846416a198c9b933704c
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
[2] http://git.openembedded.org/openembedded/log/recipes/id3lib/id3lib_3.8.3.bb
[3] http://www.openembedded.org/wiki/Mailing_lists
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl][meta-oe 06/12] liblinebreak: import from openembedded classic
Dear Denis, dear Martin,
Am Samstag, den 29.10.2011, 12:29 +0200 schrieb Martin Jansa:
From: Denis 'GNUtoo' Carikli gnu...@no-log.org
as replied to the other message please add the version and the commit
ID.
The License was verified and LIC_FILES_CHKSUM was added
Signed-off-by: Denis 'GNUtoo' Carikli gnu...@no-log.org
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
.../liblinebreak/liblinebreak_1.2.bb | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-support/liblinebreak/liblinebreak_1.2.bb
diff --git a/meta-oe/recipes-support/liblinebreak/liblinebreak_1.2.bb
b/meta-oe/recipes-support/liblinebreak/liblinebreak_1.2.bb
new file mode 100644
index 000..03c4352
--- /dev/null
+++ b/meta-oe/recipes-support/liblinebreak/liblinebreak_1.2.bb
@@ -0,0 +1,13 @@
+DESCRIPTION = Liblinebreak is an implementation of the line breaking
algorithm as described in Unicode 5.1.0 Standard Annex 14, Revision 22
+HOMEPAGE = http://vimgadgets.sourceforge.net/liblinebreak/;
+SECTION = libs
+PRIORITY = optional
+LICENSE = zlib
+LIC_FILES_CHKSUM = file://LICENCE;md5=3715191da62bafb5cfc4ff36195b2ec3
+
+SRC_URI =
${SOURCEFORGE_MIRROR}/project/vimgadgets/liblinebreak/${PV}/liblinebreak-${PV}.tar.gz
+
+inherit autotools
+
+SRC_URI[md5sum] = d18039259001ccb24b5dd4648c49c5ad
+SRC_URI[sha256sum] =
9efcb0cb1afc75ad1e92d2b2dbf4d9c77b072d6656c5f1a150af8b718d0c7b76
Reviewed-by: Paul Menzel paulepan...@users.sourceforge.net
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH meta-oe] memtester: Import from OE classic
Koen,
could you please wait at least a day until merging the patches to get
time for proper review.
Am Sonntag, den 23.10.2011, 22:40 -0500 schrieb Joel A Fernandes:
Joel, when importing recipes please add the corresponding commit ID too
as required by the commit guide lines [1].
Added LIC_FILES_CHKSUM
Signed-off-by: Joel A Fernandes joelag...@ti.com
---
This package is required by the beaglebone-tester
.../memtester/files/Makefile.patch | 15 +++
.../recipes-benchmark/memtester/memtester_4.1.3.bb | 27
2 files changed, 42 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-benchmark/memtester/files/Makefile.patch
create mode 100644 meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
diff --git a/meta-oe/recipes-benchmark/memtester/files/Makefile.patch
b/meta-oe/recipes-benchmark/memtester/files/Makefile.patch
new file mode 100644
index 000..57a0464
--- /dev/null
+++ b/meta-oe/recipes-benchmark/memtester/files/Makefile.patch
Please add a patch header.
@@ -0,0 +1,15 @@
+Index: memtester-4.0.5/Makefile
+===
+--- memtester-4.0.5.orig/Makefile2005-03-14 06:02:30.0 -0800
memtester-4.0.5/Makefile 2006-07-08 23:53:42.0 -0700
+@@ -24,8 +24,8 @@
+ auto-ccld.sh: \
+ conf-cc conf-ld warn-auto.sh
+ ( cat warn-auto.sh; \
+-echo CC=\'`head -1 conf-cc`\'; \
+-echo LD=\'`head -1 conf-ld`\' \
++echo CC=\'`head -n 1 conf-cc`\'; \
++echo LD=\'`head -n 1 conf-ld`\' \
+ ) auto-ccld.sh
+
+ compile: \
diff --git a/meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
b/meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
new file mode 100644
index 000..9f4e53e
--- /dev/null
+++ b/meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
@@ -0,0 +1,27 @@
+SECTION = console/utils
+DESCRIPTION = Utility to test for faulty memory subsystem
+LICENSE = GPLv2
The ordering is wrong and the field `HOMEPAGE` is missing [3].
+
+LIC_FILES_CHKSUM = file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3
+
+SRC_URI =
http://pyropus.ca/software/memtester/old-versions/memtester-${PV}.tar.gz;
+SRC_URI += file://Makefile.patch
+
+SRC_URI[md5sum] = e562451620cf5343016950462bc0dc38
+SRC_URI[sha256sum] =
ac56f0b6d6d6e58bcf2a3fa7f2c9b29894f5177871f21115a1906c535106acf6
+
+S = ${WORKDIR}/memtester-${PV}
This is the default.
+
+do_compile () {
+ echo '${CC} ${CFLAGS} -DPOSIX -c' conf-cc
+ echo '${CC} ${LDFLAGS}' conf-ld
+ oe_runmake
+}
+
+do_install () {
+ install -d ${D}${bindir}
+ install -d ${D}${mandir}/man8
+ install -m 0755 memtester ${D}${bindir}/
+ install -m 0755 memtester.8 ${D}${mandir}/man8/
+}
+
No empty line at the end is needed.
I fixed some of the above in OE classic. Please fix the issues mentioned
above in meta-oe with follow-up patches.
Thanks,
Paul
[1]
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Importing_from_Elsewhere
[2]
http://git.openembedded.org/openembedded/tree/recipes/memtester?id=07e215db9870db1a0f88edb328024781eb9ac852
[3] http://wiki.openembedded.org/index.php/Styleguide
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-xfce 3/3] xfce4-datetime-plugin: Initial add git (0.6.1)
Dear Andreas, Am Montag, den 24.10.2011, 20:14 +0200 schrieb Andreas Müller: Version 0.6.1 was release about 3 years ago. The patch to migrate from libxfcegui4-libxfce4ui hopefully shall be applied mainline [1]. It would have caused extra efforts to base the patch on 0.6.1 release. [1] https://bugzilla.xfce.org/show_bug.cgi?id=8064 Signed-off-by: Andreas Müller schnitzelt...@gmx.de --- .../datetime/files/port-to-libxfce4ui.patch| 360 .../datetime/xfce4-datetime-plugin_git.bb | 20 ++ 2 files changed, 380 insertions(+), 0 deletions(-) create mode 100644 meta-xfce/recipes-panel-plugins/datetime/files/port-to-libxfce4ui.patch create mode 100644 meta-xfce/recipes-panel-plugins/datetime/xfce4-datetime-plugin_git.bb […] diff --git a/meta-xfce/recipes-panel-plugins/datetime/xfce4-datetime-plugin_git.bb b/meta-xfce/recipes-panel-plugins/datetime/xfce4-datetime-plugin_git.bb new file mode 100644 index 000..831d549 --- /dev/null +++ b/meta-xfce/recipes-panel-plugins/datetime/xfce4-datetime-plugin_git.bb @@ -0,0 +1,20 @@ +DESCRIPTION = Panel plugin to date and time anc calendar when clicked the description could be improved if I am right. Panel plugin displaying date and time and a calendar when left-clicked. […] Reviewed-by: Paul Menzel paulepan...@users.sourceforge.net Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH meta-oe] memtester: Import from OE classic
Dear Joel, Am Montag, den 24.10.2011, 14:01 -0500 schrieb Joel A Fernandes: On Mon, Oct 24, 2011 at 3:05 AM, Paul Menzel wrote: .. I fixed some of the above in OE classic. Please fix the issues mentioned above in meta-oe with follow-up patches. Thanks for your review comments, I'll work on resubmitting a new patch today with the suggested changes. please note that your patch was already pushed so resubmitting is not needed and just a follow up patch. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] freetype_2.4.3.bb; Change order of configuration.
Am Samstag, den 22.10.2011, 14:28 +0200 schrieb ulf_samuels...@telia.com:
From: Ulf Samuelsson ulf_samuels...@telia.com
Build of freetype-native is broken on Ubuntu 11.10 x64 - possible others.
It works for me without problem with Debian Squeeze (32-bit). So what is
the error message in the first place?
Problem fixed in openembedded-core 2.4.4 recipe
It seems it was not present since the beginning, i. e. version 2.3.12.
Backporting the change will allow the build to complete.
openembedded-core-contrib/meta/recipes-graphics/freetype
Signed-Off-By: Ulf Samuelsson ulf.samuels...@telia.com
---
recipes/freetype/freetype_2.4.3.bb |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes/freetype/freetype_2.4.3.bb
b/recipes/freetype/freetype_2.4.3.bb
index 66d2e51..dfc1b43 100644
--- a/recipes/freetype/freetype_2.4.3.bb
+++ b/recipes/freetype/freetype_2.4.3.bb
@@ -1,7 +1,7 @@
DESCRIPTION = Freetype font rendering library
SECTION = libs
LICENSE = freetype GPLv2
-PR = r1
+PR = r2
DEPENDS = zlib
SRC_URI = \
@@ -23,9 +23,9 @@ LDFLAGS_append = -Wl,-rpath-link
-Wl,${STAGING_DIR_TARGET}${libdir}
do_configure() {
cd builds/unix
- gnu-configize --force
- aclocal -I .
libtoolize --force --copy
+ aclocal -I .
+ gnu-configize --force
autoconf
cd ${S}
oe_runconf
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] 2011.03-maintenance: Bad checksums in binutils-cross-sdk_2.18.bb
Dear Mats,
Am Freitag, den 21.10.2011, 06:42 + schrieb Mats Kärrman:
My first patch, please be gentle if i did something wrong ;)
our commit policy describes how patches should be formatted [1][2]. Most
importantly you forgot your Signed-off-by line.
The following patch is from a local branch tracking
2011.03-maintenance, should it be done different?
If I read [3] correctly it first has to go into for example the master
branch. I pushed a similar hopefully correct change there [4]. Please
send a pull request as described in [3] to get that included in
2011.03-maintenance.
The binutils_2.18 tarball from GNU has changed checksums, ref. to
thishttp://git.openembedded.org/openembedded/commit/recipes/binutils/binutils_2.18.bb?h=2011.03-maintenanceid=bc8ddbf7944f82383936d88379619aa46c3954a2
As binutils-cross-sdk_2.18.bb includes binutils_2.18.bb it does not need to
specify its own checksums.
diff --git a/recipes/binutils/binutils-cross-sdk_2.18.bb
b/recipes/binutils/binutils-cross-sdk_2.18.bb
index 837ebbe..2f13b26 100644
--- a/recipes/binutils/binutils-cross-sdk_2.18.bb
+++ b/recipes/binutils/binutils-cross-sdk_2.18.bb
@@ -1,6 +1,3 @@
require binutils_${PV}.bb
require binutils-cross-sdk.inc
PR = ${INC_PR}.1
-
-SRC_URI[md5sum] = 9d22ee4dafa3a194457caf4706f9cf01
-SRC_URI[sha256sum] =
487a33a452f0edcf1f8bb8fc23dff5c7a82edec3f3f8b65632b6c945e961ee9b
Thanks and I am looking forward to further contributions,
Paul
[1] http://www.openembedded.org/wiki/Commit_Policy
[2] http://www.openembedded.org/wiki/Category:Policy
[3] http://www.openembedded.org/wiki/2011.03-maintenance
[4]
http://git.openembedded.org/openembedded/commit/?id=f2d53aa074d76509384e7bb8a9c39e2e27210f4a
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Keeping patch status uptodate in patchwork
Dear Khem, Am Freitag, den 21.10.2011, 10:20 -0700 schrieb Khem Raj: I would like to request the patch submitter to change the status of patches appropriately particularly case where manual intervention will be needed 1. When you send pull request the cover letter is not marked accepted automatically so when pull request is merged please mark it so. I am guessing the cover letters could be filtered out automatically? It should not be useful to track those in our patch queue since they do not contain any patch. Is there a Python guru who can send a patch to Patchwork upstream? 2. When multiple versions of patches V1, V2, V3 are sent then the versions that don't get applied should be marked as superseded. Very true. It will greatly help in keeping the patchwork clean and layer maintainers and the data it represents will be lot more relevant. Please refer (new) patch submitters to the Wiki page [1]. Thanks, Paul [1] http://www.openembedded.org/wiki/Patchwork signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] 2011.03-maintenance: Bad checksums in binutils-cross-sdk_2.18.bb
Dear Ulf,
Am Freitag, den 21.10.2011, 17:05 +0200 schrieb Ulf Samuelsson:
2011-10-21 12:16, Paul Menzel skrev:
Am Freitag, den 21.10.2011, 06:42 + schrieb Mats Kärrman:
My first patch, please be gentle if i did something wrong ;)
our commit policy describes how patches should be formatted [1][2]. Most
importantly you forgot your Signed-off-by line.
The following patch is from a local branch tracking
2011.03-maintenance, should it be done different?
I did a similar fix for binutils-2.20.1, and that is apparently not the way
so this was rejected. (See other discussions on binutils this week).
I sent a new version of binutils-2.20.1 patch today,
which is taken from openembedded-core, and that
combines the new checksums, with downloading a new tarball.
If it follows the same scheme, then:
binutils-2.18.tar.bz2 is only a link to binutils-2.18a.tar.bz2
Your SRC_URI should be pointing at binutils-${PV}a.tar.bz2
you describe indeed the correct fix. Unfortunately the “wrong” fix was
already committed so I just continued on this track. I also noted that
in my commit message.
Ulf thank you for the correct fix for 2.20.1 and Mats, if you have some
time it would be great if you could send a patch for what Ulf proposed.
[…]
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Policy
[2] http://www.openembedded.org/wiki/Category:Policy
[3] http://www.openembedded.org/wiki/2011.03-maintenance
[4]
http://git.openembedded.org/openembedded/commit/?id=f2d53aa074d76509384e7bb8a9c39e2e27210f4a
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 3/3] Update checksums for binutils-2.20.1.tar.bz2
Am Donnerstag, den 20.10.2011, 00:11 +0200 schrieb Ulf Samuelsson:
2011-10-19 22:58, Paul Menzel skrev:
Am Mittwoch, den 19.10.2011, 17:10 +0200 schrieb ulf_samuels...@telia.com:
From: Ulf Samuelssonulf_samuels...@telia.com
again, please comply with our commit policy [1].
binutils: Update from 2.20.1 to 2.20.1a
Tarball is updated to 2.20.1b so checksums have changed.
I am not aware of any binutils version 2.20.1b. Do you mean 2.20.1a?
Maybe, twas from memory.
Please create a new recipe since doing it this way the already
downloaded sources would be made invalid and archives on mirrors would
cause problems too.
The recipe is not working, if the source is not downloaded yet.
Maybe a better idea is to change the URI to something useful.
Anyone knows where the original source can be downloaded?
lftp ftp.gnu.org:/gnu/binutils ls binutils-2.20.1*
lrwxrwxrwx1 3003 3003 24 Sep 01 08:40
binutils-2.20.1.tar.bz2 - binutils-2.20.1a.tar.bz2
-rw-r--r--1 3003 3002 17591527 Aug 26 07:56
binutils-2.20.1a.tar.bz2
-rw-r--r--1 3003 3002 194 Aug 26 07:56
binutils-2.20.1a.tar.bz2.sig
Just take a look at the commit Martin referenced in his reply.
Please see commit f4faecdb [2] as an example and take a look at the list
discussion [3].
Signed-off-by: Ulf Samuelssonulf.samuels...@telia.com
---
recipes/binutils/binutils_2.20.1.bb |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/recipes/binutils/binutils_2.20.1.bb
b/recipes/binutils/binutils_2.20.1.bb
index 5154e2d..0497675 100644
--- a/recipes/binutils/binutils_2.20.1.bb
+++ b/recipes/binutils/binutils_2.20.1.bb
@@ -1,7 +1,7 @@
require binutils.inc
LICENSE = GPLv3
-PR = ${INC_PR}.4
+PR = ${INC_PR}.5
EXTRA_OECONF += --disable-werror
#COMPATIBLE_TARGET_SYS = .
@@ -24,10 +24,11 @@ SRC_URI_append_nios2 = \
file://binutils-nios2.patch \
-SRC_URI[tarball.sha256sum] =
228b84722d87e88e7fdd36869e590e649ab523a0800a7d53df906498afe6f6f8
-SRC_URI[tarball.md5sum] = 9cdfb9d6ec0578c166d3beae5e15c4e5
+SRC_URI[tarball.sha256sum] =
71d37c96451333c5c0b84b170169fdcb138bbb27397dc06281905d9717c8ed64
+SRC_URI[tarball.md5sum] = 2b9dc8f2b7dbd5ec5992c6e29de0b764
# powerpc patches
SRC_URI += \
file://binutils-2.16.1-e300c2c3.patch \
+
Please remove the newly added line.
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Policy
[2]
http://git.openembedded.org/openembedded/commit/?id=f4faecdbd0b7c83e5787735ef1495a34aca861e4
[3]
http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-September/034885.html
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 1/3] Backport openssl-1.0.0e from meta-openembedded
Dear Ulf,
Am Mittwoch, den 19.10.2011, 17:10 +0200 schrieb ulf_samuels...@telia.com:
From: Ulf Samuelsson ulf_samuels...@telia.com
please amend the commit summary and make it compliant to our commit
policy [1].
openssl: Add version 1.0.0e (backport from meta-openembedded)
Please also include the revision or URL to the commit you took this
from.
I am build testing this right now. For easier review it would be nice if
you could add this information to the commit message too.
Signed-off-by: Ulf Samuelsson ulf.samuels...@telia.com
---
.../include/angstrom-2010-preferred-versions.inc |4 +-
.../openssl/openssl-1.0.0e/configure-targets.patch | 31 +
.../openssl-1.0.0e/debian/c_rehash-compat.patch| 43 +
recipes/openssl/openssl-1.0.0e/debian/ca.patch | 20 +
.../openssl-1.0.0e/debian/debian-targets.patch | 52 +
.../openssl-1.0.0e/debian/make-targets.patch | 13 +
.../openssl/openssl-1.0.0e/debian/man-dir.patch| 13 +
.../openssl-1.0.0e/debian/man-section.patch| 32 +
.../openssl/openssl-1.0.0e/debian/no-rpath.patch | 13 +
.../openssl-1.0.0e/debian/no-symbolic.patch| 13 +
recipes/openssl/openssl-1.0.0e/debian/pic.patch| 240 ++
.../openssl/openssl-1.0.0e/debian/pkg-config.patch | 34 +
.../openssl-1.0.0e/debian/version-script.patch | 4509
.../engines-install-in-libdir-ssl.patch| 53 +
recipes/openssl/openssl-1.0.0e/oe-ldflags.patch| 22 +
.../openssl/openssl-1.0.0e/openssl-fix-link.patch | 35 +
.../openssl/openssl-1.0.0e/parallel-make-fix.patch | 20 +
recipes/openssl/openssl-1.0.0e/shared-libs.patch | 48 +
recipes/openssl/openssl-native_1.0.0e.bb | 39 +
recipes/openssl/openssl.inc|9 +-
recipes/openssl/openssl_1.0.0e.bb | 46 +
21 files changed, 5284 insertions(+), 5 deletions(-)
create mode 100644 recipes/openssl/openssl-1.0.0e/configure-targets.patch
create mode 100644
recipes/openssl/openssl-1.0.0e/debian/c_rehash-compat.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/ca.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/debian-targets.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/make-targets.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/man-dir.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/man-section.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/no-rpath.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/no-symbolic.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/pic.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/pkg-config.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/debian/version-script.patch
create mode 100644
recipes/openssl/openssl-1.0.0e/engines-install-in-libdir-ssl.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/oe-ldflags.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/openssl-fix-link.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/parallel-make-fix.patch
create mode 100644 recipes/openssl/openssl-1.0.0e/shared-libs.patch
create mode 100644 recipes/openssl/openssl-native_1.0.0e.bb
create mode 100644 recipes/openssl/openssl_1.0.0e.bb
[…]
diff --git a/recipes/openssl/openssl-native_1.0.0e.bb
b/recipes/openssl/openssl-native_1.0.0e.bb
new file mode 100644
index 000..8be5bcb
--- /dev/null
+++ b/recipes/openssl/openssl-native_1.0.0e.bb
@@ -0,0 +1,39 @@
+require openssl.inc
+
+inherit pkgconfig native
+
+SRC_URI[src.md5sum] = 7040b89c4c58c7a1016c0dfa6e821c86
+SRC_URI[src.sha256sum] =
e361dc2775733fb84de7b5bf7b504778b772869e8f7bfac0b28b935cbf7380f7
+PR = ${INC_PR}.0
+
+DEFAULT_PREFERENCE = -1
This seems strange, since this is not set in the “normal” recipe.
+export DIRS = crypto ssl apps engines
+
+# This flag can contain target options (e.g -mfpu=neon for armv7-a systems)
+export FULL_OPTIMIZATION =
+export BUILD_OPTIMIZATION =
+
+SRC_URI += file://configure-targets.patch \
+file://shared-libs.patch \
+file://oe-ldflags.patch \
+file://engines-install-in-libdir-ssl.patch \
+file://openssl-fix-link.patch \
+file://debian/version-script.patch \
+file://debian/pic.patch \
+file://debian/c_rehash-compat.patch \
+file://debian/ca.patch \
+file://debian/make-targets.patch \
+file://debian/no-rpath.patch \
+file://debian/man-dir.patch \
+file://debian/man-section.patch \
+file://debian/pkg-config.patch \
+file://debian/no-symbolic.patch \
+file://debian/debian-targets.patch \
+
+
+PARALLEL_MAKE =
+
+CFLAG += -Wa,--noexecstack
+
+NATIVE_INSTALL_WORKS = 1
diff --git a/recipes/openssl/openssl.inc b/recipes/openssl/openssl.inc
Re: [oe] [PATCH 3/3] Update checksums for binutils-2.20.1.tar.bz2
Dear Ulf,
Am Mittwoch, den 19.10.2011, 17:10 +0200 schrieb ulf_samuels...@telia.com:
From: Ulf Samuelsson ulf_samuels...@telia.com
again, please comply with our commit policy [1].
binutils: Update from 2.20.1 to 2.20.1a
Tarball is updated to 2.20.1b so checksums have changed.
I am not aware of any binutils version 2.20.1b. Do you mean 2.20.1a?
Please create a new recipe since doing it this way the already
downloaded sources would be made invalid and archives on mirrors would
cause problems too.
Please see commit f4faecdb [2] as an example and take a look at the list
discussion [3].
Signed-off-by: Ulf Samuelsson ulf.samuels...@telia.com
---
recipes/binutils/binutils_2.20.1.bb |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/recipes/binutils/binutils_2.20.1.bb
b/recipes/binutils/binutils_2.20.1.bb
index 5154e2d..0497675 100644
--- a/recipes/binutils/binutils_2.20.1.bb
+++ b/recipes/binutils/binutils_2.20.1.bb
@@ -1,7 +1,7 @@
require binutils.inc
LICENSE = GPLv3
-PR = ${INC_PR}.4
+PR = ${INC_PR}.5
EXTRA_OECONF += --disable-werror
#COMPATIBLE_TARGET_SYS = .
@@ -24,10 +24,11 @@ SRC_URI_append_nios2 = \
file://binutils-nios2.patch \
-SRC_URI[tarball.sha256sum] =
228b84722d87e88e7fdd36869e590e649ab523a0800a7d53df906498afe6f6f8
-SRC_URI[tarball.md5sum] = 9cdfb9d6ec0578c166d3beae5e15c4e5
+SRC_URI[tarball.sha256sum] =
71d37c96451333c5c0b84b170169fdcb138bbb27397dc06281905d9717c8ed64
+SRC_URI[tarball.md5sum] = 2b9dc8f2b7dbd5ec5992c6e29de0b764
# powerpc patches
SRC_URI += \
file://binutils-2.16.1-e300c2c3.patch \
+
Please remove the newly added line.
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Policy
[2]
http://git.openembedded.org/openembedded/commit/?id=f4faecdbd0b7c83e5787735ef1495a34aca861e4
[3]
http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-September/034885.html
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-efl 3/3] lightmediascanner: Add version 0.4.4 (initial recipe)
Am Dienstag, den 18.10.2011, 16:10 +0200 schrieb Martin Jansa: From: pespin pespin.s...@gmail.com The name is still not correct. Although the Signed-off-by line is. Please correct that. * Copied from oe-classic http://git.openembedded.org/openembedded/commit/?id=63d3969b0f839fc4b7bf7fe836daec729d9d3c53 * Remove PE=1 * Add LIC_FILES_CHKSUM * Builds fine using SHR distro * JaMa: removed PR Was the recipe tested somehow? Signed-off-by: Pau Espin Pedrol pespin.s...@gmail.com Signed-off-by: Martin Jansa martin.ja...@gmail.com --- .../lightmediascanner/lightmediascanner_0.4.4.bb | 27 1 files changed, 27 insertions(+), 0 deletions(-) create mode 100644 meta-efl/recipes-multimedia/lightmediascanner/lightmediascanner_0.4.4.bb […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] minimal-uclibc: ../../src/lib/.libs/liblightmediascanner.so: undefined reference to `libiconv_open' (was: [meta-efl] lightmediascanner: Add version 0.4.3.0 (initial recipe))
Am Sonntag, den 16.10.2011, 21:30 +0200 schrieb Denis 'GNUtoo' Carikli: The upstream developer Gustavo provided a patch and this seems to fix the build issues. Could you test if the recipe in oe.dev [1] works for you. it doesn't work for me: | configure.ac:37: required file `./config.rpath' not found | autoreconf: automake failed with exit status: 1 What recipe did you use? The recipe for 0.4.3.0 in OE-classic takes care of that [1]! Please be more elaborate next time and adapt the subject line too if the message content is different. and at line 37 there is: AM_ICONV which is added by that patch. 0.4.3.0 should be fine. Anyway I pushed 0.4.4 in commit 63d3969b [2]. Thanks, Paul [1] http://git.openembedded.org/openembedded/tree/recipes/lightmediascanner/lightmediascanner_0.4.3.0.bb?id=63d3969b0f839fc4b7bf7fe836daec729d9d3c53#n18 [2] http://git.openembedded.org/openembedded/commit/?id=63d3969b0f839fc4b7bf7fe836daec729d9d3c53 signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2] lightmediascanner: Add version 0.4.3.0 (initial recipe)
Dear Denis, dear Pau, Am Sonntag, den 16.10.2011, 21:37 +0200 schrieb Denis 'GNUtoo' Carikli: From: pespin pespin.s...@gmail.com please use a correct name. * Recipe based on recipe v0.4.1.0 from oe.dev (http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/lightmediascanner/lightmediascanner_0.4.1.0.bb?id=99ed67320060c4b9f686328a22f68980c2154c62) NAK. Please use 0.4.4 [1]. Signed-off-by: Pau Espin Pedrol pespin.s...@gmail.com Signed-off-by: Denis 'GNUtoo' Carikli gnu...@no-log.org --- .../lightmediascanner/lightmediascanner_0.4.3.0.bb | 28 1 files changed, 28 insertions(+), 0 deletions(-) create mode 100644 meta-efl/recipes-multimedia/lightmediascanner/lightmediascanner_0.4.3.0.bb […] Thanks, Paul [1] http://git.openembedded.org/openembedded/commit/?id=63d3969b0f839fc4b7bf7fe836daec729d9d3c53 signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] git server move
Dear OE folks, Am Dienstag, den 11.10.2011, 21:26 +0200 schrieb Paul Menzel: Am Dienstag, den 11.10.2011, 15:11 -0400 schrieb Cliff Brake: Hi, we are moving git.openembedded.org to a new server. is there more information about the reasons? Is it just a new machine? Where is it hosted now? SSH access on the old server has been disabled. git:// still works there. As soon as DNS propagates, SSH access will work with the new server. Let me know if you see any problems. SSH keys will likely change, so expect messages about that. So what are the fingerprints of the new keys? ;-) I hope the new fingerprint is the following. ed:99:0d:c1:6e:6c:02:75:df:36:25:4d:62:39:b7:e5 Looking at what happened at kernel.org I would have hoped to get an earlier response. Or do I miss something here that the fingerprint is not important? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can someone pls prune a few obsolete branches in openembedded?
Dear Ulf, Am Mittwoch, den 12.10.2011, 09:10 +0200 schrieb Ulf Samuelsson: All the branches: ulf/linux-2.6.30* and ulf/test are no longer in use. All the stuff is already in mainline. Can someone please remove them? Is for example `git push origin :ulf/test` not working? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] git server move: new server key fingerprints
Am Mittwoch, den 12.10.2011, 10:44 -0400 schrieb Cliff Brake: On Tue, Oct 11, 2011 at 3:26 PM, Paul Menzel wrote: […] So what are the fingerprints of the new keys? ;-) 1024 ad:8e:65:4e:dc:4c:d9:63:8f:67:b3:87:03:c9:a1:73 ssh_host_dsa_key.pub (DSA) 2048 ed:99:0d:c1:6e:6c:02:75:df:36:25:4d:62:39:b7:e5 ssh_host_rsa_key.pub (RSA) Let me know if you have any more questions. Thank you for doing the work and sharing the key. It is much appreciated. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] bluez4_4.95.bb: new recipe for building bluez-4.95
Dear Vita,
thank you for your patch.
Am Dienstag, den 11.10.2011, 11:08 +0200 schrieb Vita Preskovsky:
Using
bluez4: Add version 4.95
as the commit summary would be cleaner. Use `git commit --amend` to
change that.
Additionally you should elaborate more in the commit message what the
patch is doing.
1. Have you tested it? Is it just an upgrade because of or does version
4.91 in the repository have any short comings so that it should be
removed?
Signed-off-by: Vita Preskovsky vi...@ti.com
---
recipes/bluez/bluez4_4.95.bb | 30 ++
1 files changed, 30 insertions(+), 0 deletions(-)
create mode 100644 recipes/bluez/bluez4_4.95.bb
diff --git a/recipes/bluez/bluez4_4.95.bb b/recipes/bluez/bluez4_4.95.bb
new file mode 100644
index 000..a682d6a
--- /dev/null
+++ b/recipes/bluez/bluez4_4.95.bb
@@ -0,0 +1,30 @@
+require bluez4.inc
+SRC_URI = \
+ http://www.kernel.org/pub/linux/bluetooth/bluez-${PV}.tar.gz \
2. As far as I know kernel.org after the compromise presently does not
provide that archive. So the recipe will not build unless there is a
mirror somewhere. Do you know of a mirror?
+ file://bluetooth.conf \
+
+
+SRC_URI[md5sum] = 341294b2849a04a4afff5c96bfbf30b2
+SRC_URI[sha256sum] =
d6ea9de410fc2bcd2620d709c2202893b218e2e6a55c3c0ce6bebd27fa4120f6
+
+DEFAULT_PREFERENCE = -1
3. Why?
+DEFAULT_PREFERENCE_angstrom = 1
4. Have you talked to the Ȧngström maintainers?
+
+DEPENDS += libsndfile1
+
+PR = ${INC_PR}.0
+
+# Not all distros have a recent enough udev
+BTUDEV = --disable-udevrules
+BTUDEV_angstrom = --enable-udevrules
+BTUDEV_shr = --enable-udevrules
+
+EXTRA_OECONF += ${BTUDEV}
+do_configure_append(){
+ echo #define LIBUDEV_I_KNOW_THE_API_IS_SUBJECT_TO_CHANGE
${S}/config.h
+}
+
+FILES_${PN}-dbg += \
+ ${base_libdir}/udev/.debug \
+ ${libdir}/*/.debug \
+
Otherwise this recipe looks good. Is it planned for branch
2011.03-maintenance?
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] git server move
Dear Cliff, Am Dienstag, den 11.10.2011, 15:11 -0400 schrieb Cliff Brake: Hi, we are moving git.openembedded.org to a new server. is there more information about the reasons? Is it just a new machine? Where is it hosted now? SSH access on the old server has been disabled. git:// still works there. As soon as DNS propagates, SSH access will work with the new server. Let me know if you see any problems. SSH keys will likely change, so expect messages about that. So what are the fingerprints of the new keys? ;-) Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] ldconfig-native: Change the license field
Am Freitag, den 07.10.2011, 10:39 -0700 schrieb Khem Raj: The license should be GPLv2+ Koen has already committed this in 2f04e069 [1]. I have to remarks. 1. Combining your commit summary and message to ldconfig-native Correct license field to GPLv2+ would be better next time. Especially if looking at the commit log with `--format=oneline` or on the Web. Signed-off-by: Khem Raj raj.k...@gmail.com --- .../recipes-core/eglibc/ldconfig-native_2.12.1.bb |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-oe/recipes-core/eglibc/ldconfig-native_2.12.1.bb b/meta-oe/recipes-core/eglibc/ldconfig-native_2.12.1.bb index 00edb6e..2a93913 100644 --- a/meta-oe/recipes-core/eglibc/ldconfig-native_2.12.1.bb +++ b/meta-oe/recipes-core/eglibc/ldconfig-native_2.12.1.bb @@ -1,6 +1,6 @@ DESCRIPTION = A standalone native ldconfig build -LICENSE = GPLv2.1 +LICENSE = GPLv2+ […] 2. Looking at the source headers of for example `cache.c` /* Copyright (C) 1999-2003,2005,2006,2007 Free Software Foundation, Inc. This file is part of the GNU C Library. Contributed by Andreas Jaeger a...@suse.de, 1999. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ the license is GPLv2+ as you changed it to. But in `readelflib.c` we have /* Copyright (C) 1999, 2000, 2001, 2002, 2007 Free Software Foundation, Inc. This file is part of the GNU C Library. Contributed by Andreas Jaeger a...@suse.de, 1999 and Jakub Jelinek ja...@redhat.com, 1999. The GNU C Library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. The GNU C Library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with the GNU C Library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. */ which is LGPLv2.1+. Also `dl-cache.c` has the `LGPLv2.1+` license header. So should the field be changed to `LICENSE = GPLv2+ LGPL`? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] Added ImageMagick 6.7.2-3
Dear Gavin,
thank you for your patch.
Am Donnerstag, den 06.10.2011, 16:01 -0700 schrieb gavinswan...@gmail.com:
From: Gavin Swanson gavinswan...@gmail.com
Please refer to our commit policy [1] and style guide [2].
(Unfortunately the Wiki is down at the moment.)
Change the commit summary to
imagemagick: Add version 6.7.2-3
and add some more information to the commit message. What distribution
and machine did you use for testing? Have you run tested the new
version.
You seem to have used an existing recipe as a template. Please note that
too.
At last please add you Signed-off-by line.
---
recipes/imagemagick/imagemagick_6.7.2-3.bb | 36
1 files changed, 36 insertions(+), 0 deletions(-)
create mode 100644 recipes/imagemagick/imagemagick_6.7.2-3.bb
diff --git a/recipes/imagemagick/imagemagick_6.7.2-3.bb
b/recipes/imagemagick/imagemagick_6.7.2-3.bb
new file mode 100644
index 000..14746c9
--- /dev/null
+++ b/recipes/imagemagick/imagemagick_6.7.2-3.bb
@@ -0,0 +1,36 @@
+DESCRIPTION = ImageMagick is an image convertion tools
+SECTION = console/utils
+LICENSE = GPL
I updated those meta fields in the repository. Please update the above
too.
+# FIXME: There is much more checked libraries. All should be added or
explicitly disabled to get consistent results.
+DEPENDS = lcms bzip2 jpeg libpng librsvg tiff zlib
+
+PR = r1
Please start with `r0`.
+
+SRC_URI = ftp://ftp.nluug.nl/pub/ImageMagick/ImageMagick-${PV}.tar.bz2 \
+# file://PerlMagic_MakePatch;apply=yes \
Why is this patch not needed anymore? You can just delete the line then.
+
+
+IMVER = 6.7.2-3
I think the old recipes strip the `-3` to get the correct directory
names. This way `IMVER` is equal to `PN`.
+
+S = ${WORKDIR}/ImageMagick-${IMVER}
It looks like you can delete this line for this version, since in your
version the archive seems to have a “correctly” named folder included.
$ ls minimal-dev/work/armv7a-oe-linux-gnueabi/imagemagick-6.4.4-1-r7/
ImageMagick-6.4.4 temp
$ ls minimal-dev/work/armv7a-oe-linux-gnueabi/imagemagick-6.7.2-3-r1/
ImageMagick-6.7.2-3 temp
+
+inherit autotools binconfig pkgconfig
+
+EXTRA_OECONF = --program-prefix= --without-x --without-freetype
--without-perl --disable-openmp
+
+FILES_${PN} += ${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.so \
+${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.la \
+${libdir}/ImageMagick-${IMVER}/config/ \
+${datadir}/ImageMagick-${IMVER}
Could you please look into the following warnings.
NOTE: package imagemagick-6.7.2-3-r1: task do_qa_staging: Succeeded
WARNING: the following files were installed but not shipped in any
package:
WARNING: /usr/share/ImageMagick-6.7.2/francais.xml
WARNING: /usr/share/ImageMagick-6.7.2/locale.xml
WARNING: /usr/share/ImageMagick-6.7.2/english.xml
WARNING: /usr/share/ImageMagick-6.7.2/configure.xml
Here you can also see that the directory name seems to only include
6.7.2 instead of 6.7.2-3. So you should check where `IMVER` should be
used and where `PV`, which is 6.7.2-3.
+
+FILES_${PN}-dev += ${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.a
+
+FILES_${PN}-dbg += ${libdir}/ImageMagick-${IMVER}/modules-Q16/*/.debug/*
+
+BBCLASSEXTEND = native
+
+LEAD_SONAME = libMagickCore.so.*
+
+
+SRC_URI[md5sum] = 62e12090d2d385f4800c06f58f477bea
+SRC_URI[sha256sum] =
50fe6e1af9e900e5d4bef45879a3a7e15512bb9ab3dbbafb521825359cb6d2c7
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Policy
[2] http://www.openembedded.org/index.php?title=Styleguide
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] Added ImageMagick 6.7.2-3
Am Freitag, den 07.10.2011, 09:38 -0700 schrieb Gavin Swanson:
This is my first attempt at submitting a patch. Please bear with me.
I will. Thank you for following up on my review comments.
I read through the style guide and used the oe-stylize script on my
changed version. I still have some questions.
On Fri, Oct 7, 2011 at 3:01 AM, Paul Menzel wrote:
Am Donnerstag, den 06.10.2011, 16:01 -0700 schrieb gavinswan...@gmail.com:
From: Gavin Swanson gavinswan...@gmail.com
Please refer to our commit policy [1] and style guide [2].
(Unfortunately the Wiki is down at the moment.)
Change the commit summary to
imagemagick: Add version 6.7.2-3
and add some more information to the commit message. What distribution
and machine did you use for testing? Have you run tested the new
version.
You seem to have used an existing recipe as a template. Please note that
too.
At last please add you Signed-off-by line.
---
recipes/imagemagick/imagemagick_6.7.2-3.bb | 36
1 files changed, 36 insertions(+), 0 deletions(-)
create mode 100644 recipes/imagemagick/imagemagick_6.7.2-3.bb
diff --git a/recipes/imagemagick/imagemagick_6.7.2-3.bb
b/recipes/imagemagick/imagemagick_6.7.2-3.bb
new file mode 100644
index 000..14746c9
--- /dev/null
+++ b/recipes/imagemagick/imagemagick_6.7.2-3.bb
@@ -0,0 +1,36 @@
+DESCRIPTION = ImageMagick is an image convertion tools
+SECTION = console/utils
+LICENSE = GPL
I updated those meta fields in the repository. Please update the above
too.
I'm using the gumstix repo,
Please include such information in your commit message.
so I didn't have these changes, I looked them up though and have
included them.
Great. I am sorry for the hassle.
[…]
+
+SRC_URI = ftp://ftp.nluug.nl/pub/ImageMagick/ImageMagick-${PV}.tar.bz2 \
+# file://PerlMagic_MakePatch;apply=yes \
Why is this patch not needed anymore? You can just delete the line then.
Not sure why it was needed in the first place, but it builds and runs
fine without it.
+
+
+IMVER = 6.7.2-3
I think the old recipes strip the `-3` to get the correct directory
names. This way `IMVER` is equal to `PN`.
The build does not succeed without the -3 in it
What was the error? But as noted below, they seem to have changed the
directory name in the source archive.
+
+S = ${WORKDIR}/ImageMagick-${IMVER}
It looks like you can delete this line for this version, since in your
version the archive seems to have a “correctly” named folder included.
This line has been removed with success
$ ls minimal-dev/work/armv7a-oe-linux-gnueabi/imagemagick-6.4.4-1-r7/
ImageMagick-6.4.4 temp
$ ls minimal-dev/work/armv7a-oe-linux-gnueabi/imagemagick-6.7.2-3-r1/
ImageMagick-6.7.2-3 temp
+
+inherit autotools binconfig pkgconfig
+
+EXTRA_OECONF = --program-prefix= --without-x --without-freetype
--without-perl --disable-openmp
+
+FILES_${PN} += ${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.so \
+${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.la \
+${libdir}/ImageMagick-${IMVER}/config/ \
+${datadir}/ImageMagick-${IMVER}
Could you please look into the following warnings.
NOTE: package imagemagick-6.7.2-3-r1: task do_qa_staging: Succeeded
WARNING: the following files were installed but not shipped in any
package:
WARNING: /usr/share/ImageMagick-6.7.2/francais.xml
WARNING: /usr/share/ImageMagick-6.7.2/locale.xml
WARNING: /usr/share/ImageMagick-6.7.2/english.xml
WARNING: /usr/share/ImageMagick-6.7.2/configure.xml
Not sure where those warnings show up for you, I don't get them during
the build, is there some kind of extra warnings flag I should be
using?
I am using `minimal` (EGLIBC) for `MACHINE = beagleboard`. Are these
files included in your final package?
Here you can also see that the directory name seems to only include
6.7.2 instead of 6.7.2-3. So you should check where `IMVER` should be
used and where `PV`, which is 6.7.2-3.
Not sure what you mean by this. As stated the build fails without the
-3 on the IMVER
As seen with the warnings above, there seems to be a directory where the
`-3` needs to be stripped. You should use `PV` instead of `IMVER` where
possible like below too.
+
+FILES_${PN}-dev += ${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.a
+
+FILES_${PN}-dbg += ${libdir}/ImageMagick-${IMVER}/modules-Q16/*/.debug/*
+
+BBCLASSEXTEND = native
+
+LEAD_SONAME = libMagickCore.so.*
+
+
+SRC_URI[md5sum] = 62e12090d2d385f4800c06f58f477bea
+SRC_URI[sha256sum] =
50fe6e1af9e900e5d4bef45879a3a7e15512bb9ab3dbbafb521825359cb6d2c7
Thanks,
Paul
[1] http://www.openembedded.org/wiki/Commit_Policy
[2] http://www.openembedded.org/index.php?title=Styleguide
signature.asc
Description
Re: [oe] [PATCH] Added ImageMagick 6.7.2-3
Am Freitag, den 07.10.2011, 18:58 +0200 schrieb Paul Menzel:
Am Freitag, den 07.10.2011, 09:38 -0700 schrieb Gavin Swanson:
This is my first attempt at submitting a patch. Please bear with me.
I will. Thank you for following up on my review comments.
I read through the style guide and used the oe-stylize script on my
changed version. I still have some questions.
On Fri, Oct 7, 2011 at 3:01 AM, Paul Menzel wrote:
Am Donnerstag, den 06.10.2011, 16:01 -0700 schrieb gavinswan...@gmail.com:
From: Gavin Swanson gavinswan...@gmail.com
Please refer to our commit policy [1] and style guide [2].
(Unfortunately the Wiki is down at the moment.)
Change the commit summary to
imagemagick: Add version 6.7.2-3
and add some more information to the commit message. What distribution
and machine did you use for testing? Have you run tested the new
version.
You seem to have used an existing recipe as a template. Please note that
too.
At last please add you Signed-off-by line.
---
recipes/imagemagick/imagemagick_6.7.2-3.bb | 36
1 files changed, 36 insertions(+), 0 deletions(-)
create mode 100644 recipes/imagemagick/imagemagick_6.7.2-3.bb
diff --git a/recipes/imagemagick/imagemagick_6.7.2-3.bb
b/recipes/imagemagick/imagemagick_6.7.2-3.bb
new file mode 100644
index 000..14746c9
--- /dev/null
+++ b/recipes/imagemagick/imagemagick_6.7.2-3.bb
@@ -0,0 +1,36 @@
+DESCRIPTION = ImageMagick is an image convertion tools
+SECTION = console/utils
+LICENSE = GPL
I updated those meta fields in the repository. Please update the above
too.
I'm using the gumstix repo,
Please include such information in your commit message.
so I didn't have these changes, I looked them up though and have
included them.
Great. I am sorry for the hassle.
[…]
+
+SRC_URI = ftp://ftp.nluug.nl/pub/ImageMagick/ImageMagick-${PV}.tar.bz2
\
+# file://PerlMagic_MakePatch;apply=yes \
Why is this patch not needed anymore? You can just delete the line then.
Not sure why it was needed in the first place, but it builds and runs
fine without it.
+
+
+IMVER = 6.7.2-3
I think the old recipes strip the `-3` to get the correct directory
names. This way `IMVER` is equal to `PN`.
The build does not succeed without the -3 in it
What was the error? But as noted below, they seem to have changed the
directory name in the source archive.
+
+S = ${WORKDIR}/ImageMagick-${IMVER}
It looks like you can delete this line for this version, since in your
version the archive seems to have a “correctly” named folder included.
This line has been removed with success
Are you sure? Testing this, it looks like the default is to make
everything lower case and it broke for me.
| + do_install
| + autotools_do_install
| + oe_runmake
DESTDIR=/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/imagemagick-6.7.2-3-r1/image
install
| + oenote make
DESTDIR=/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/imagemagick-6.7.2-3-r1/image
install
| + echo NOTE: 'make
DESTDIR=/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/imagemagick-6.7.2-3-r1/image
install'
| NOTE: make
DESTDIR=/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/imagemagick-6.7.2-3-r1/image
install
| + make
DESTDIR=/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/imagemagick-6.7.2-3-r1/image
install
| make: *** No rule to make target `install'. Stop.
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL: 'oe_runmake failed'
| FATAL: oe_runmake failed
| + exit 1
$ ls minimal-dev/work/armv7a-oe-linux-gnueabi/imagemagick-6.4.4-1-r7/
ImageMagick-6.4.4 temp
$ ls minimal-dev/work/armv7a-oe-linux-gnueabi/imagemagick-6.7.2-3-r1/
ImageMagick-6.7.2-3 temp
+
+inherit autotools binconfig pkgconfig
+
+EXTRA_OECONF = --program-prefix= --without-x --without-freetype
--without-perl --disable-openmp
+
+FILES_${PN} += ${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.so \
+${libdir}/ImageMagick-${IMVER}/modules-Q16/*/*.la \
+${libdir}/ImageMagick-${IMVER}/config/ \
+${datadir}/ImageMagick-${IMVER}
Could you please look into the following warnings.
NOTE: package imagemagick-6.7.2-3-r1: task do_qa_staging: Succeeded
WARNING: the following files were installed but not shipped in any
package:
WARNING: /usr/share/ImageMagick-6.7.2/francais.xml
WARNING: /usr/share/ImageMagick-6.7.2/locale.xml
WARNING: /usr/share/ImageMagick-6.7.2/english.xml
WARNING: /usr/share/ImageMagick-6.7.2/configure.xml
Not sure where those warnings show up
Re: [oe] [PATCH] iw: build version 0.9.22 from git sources
Dear Eyal,
Am Montag, den 26.09.2011, 11:27 +0300 schrieb Eyal Reizer:
how has this recipe been tested?
Signed-off-by: Eyal Reizer ey...@ti.com
---
recipes/iw/iw_git.bb | 29 +
1 files changed, 29 insertions(+), 0 deletions(-)
create mode 100644 recipes/iw/iw_git.bb
diff --git a/recipes/iw/iw_git.bb b/recipes/iw/iw_git.bb
new file mode 100644
index 000..e4d0cd5
--- /dev/null
+++ b/recipes/iw/iw_git.bb
@@ -0,0 +1,29 @@
+DESCRIPTION = nl80211 based CLI configuration utility for wireless devices
+HOMEPAGE = http://linuxwireless.org/en/users/Documentation/iw;
+SECTION = base
+PRIORITY = optional
+LICENSE = BSD
Could you create a inc file to not duplicate the header and the
overrides below? Or can 0.9.20 be removed?
+
+SRCREV = 0a236ef5f8e4ba7218aac7d0cdacf45673d5b35c
+PR = r1
Please start with `r0`.
+PV = 0.9.22
+PR_append = +gitr${SRCPV}
+
+DEPENDS = libnl pkgconfig
+
+SRC_URI = \
+ git://git.sipsolutions.net/iw.git;protocol=git \
+
+CFLAGS += -DCONFIG_LIBNL20
+
+S = ${WORKDIR}/git/
+
+do_compile() {
+ oe_runmake
+}
+
+do_install() {
+ oe_runmake DESTDIR=${D} install
+}
+
+
Please remove the new lines at the end.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe] WIP: cloud9: created
Dear Jason,
Am Samstag, den 24.09.2011, 03:08 -0400 schrieb Jason Kridner:
Cloud9 is a web-browser based IDE. This application should support
multiple architectures as long as they have node.js and a build of
node-o3-xml that is dropped into this system. Ideally, that library
would be added separately as a system-dependent portion, because
everything else should be ISA independent.
Advice on cleaning up this recipe is welcome.
what problems to do you see?
I will continue to improve it as I understand how. It is rather
useful as-is.
---
meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb | 28
+++
1 files changed, 28 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb
diff --git a/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb
b/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb
new file mode 100644
index 000..626332f
--- /dev/null
+++ b/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb
@@ -0,0 +1,28 @@
+DESCRIPTION = Meet Cloud9, development-as-a-service for Javascripters and
other developers
+HOMEPAGE = http://c9.io;
+RDEPENDS = nodejs
This belongs further down too.
+
+SRC_URI = git://github.com/jadonk/cloud9.git;protocol=git \
+
Please put that below the license stuff [1].
+
+LICENSE = GPLv3
+LIC_FILES_CHKSUM = file://LICENSE;md5=4784c3bcff601fd8f9515f52a11e7018
+
+SRCREV = 08bae1d1cc2ba9f7f883a25afd07f0339a82fa8b
+S = ${WORKDIR}/git
+
+do_configure_prepend () {
+ git submodule update --init --recursive
+}
+
+do_compile () {
+}
Maybe add comments why the above overrides are needed.
+
+do_install () {
+ install -m 0755 -d ${D}/usr/share/cloud9 ${D}${bindir}
+ rsync -r --exclude=.* ${S}/* ${D}/usr/share/cloud9
Should `rsync` be put in `DEPENDS`?
+ touch ${D}${bindir}/cloud9
+ echo #!/bin/sh ${D}${bindir}/cloud9
+ echo node /usr/share/cloud9/bin/cloud9.js -l 0.0.0.0 -w /home/root -p
3000 ${D}${bindir}/cloud9
+ chmod 0755 ${D}${bindir}/cloud9
+}
Thanks,
Paul
[1] http://openembedded.org/index.php?title=Styleguide
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v4] libroxml: Add version 2.1.1
Am Donnerstag, den 22.09.2011, 10:57 +0200 schrieb Tristan Lelong:
libroxml is a small fast and powerful xml library
build successfully using org.openembedded.dev with DISTRO=minimal and MACHINE
= i686-generic
build successfully using org.openembedded.dev with DISTRO=minimal and MACHINE
= ppce500v2
tested using projects unit tests on powerpc binaries
Signed-off-by: Tristan Lelong tristan.lel...@blunderer.org
---
recipes/libroxml/libroxml.inc | 24
recipes/libroxml/libroxml_2.1.1.bb |5 +
2 files changed, 29 insertions(+), 0 deletions(-)
create mode 100644 recipes/libroxml/libroxml.inc
create mode 100644 recipes/libroxml/libroxml_2.1.1.bb
diff --git a/recipes/libroxml/libroxml.inc b/recipes/libroxml/libroxml.inc
new file mode 100644
index 000..2ee03eb
--- /dev/null
+++ b/recipes/libroxml/libroxml.inc
@@ -0,0 +1,24 @@
+DESCRIPTION = Small, fast and powerful xml library
+AUTHOR = Tristan Lelong tristan.lel...@libroxml.net
+HOMEPAGE = http://www.libroxml.net;
+SECTION = libs
+PRIORITY = optional
+LICENSE = LGPLv2.1+
+INC_PR = r0
+
+SRC_URI = http://libroxml.googlecode.com/files/${P}.tar.gz;
+
+do_install() {
+ install -D -m 755 ${S}/roxml ${D}/${bindir}/roxml
+ install -D -m 755 ${S}/libroxml.so.0 ${D}/${libdir}/libroxml.so.0
+ install -D -m 644 ${S}/libroxml.a ${D}/${libdir}/libroxml.a
+ install -D -m 644 ${S}/inc/roxml.h ${D}/${includedir}/roxml.h
+ ln -s libroxml.so.0 ${D}/${libdir}/libroxml.so
+}
+
+PACKAGES += roxml roxml-dbg
+FILES_${PN} = ${libdir}/libroxml.so.0
+FILES_${PN}-dev = ${libdir}/libroxml.a ${libdir}/libroxml.so
${includedir}/roxml.h
+FILES_${PN}-dbg = ${libdir}/.debug/libroxml.so.0
+FILES_roxml = ${bindir}/roxml
+FILES_roxml-dbg = ${bindir}/.debug/roxml
I edited this to
+PACKAGES =+ roxml roxml-dbg
+FILES_roxml = ${bindir}/*
+FILES_roxml-dbg = ${bindir}/.debug/*
and committed this in 9e1aa4d0 [1].
The only difference I could spot is, that `libroxml.a` is packaged in
`libroxml-static`. I hope that is fine with you and I did not mess
anything up.
diff --git a/recipes/libroxml/libroxml_2.1.1.bb
b/recipes/libroxml/libroxml_2.1.1.bb
new file mode 100644
index 000..c47e1b7
--- /dev/null
+++ b/recipes/libroxml/libroxml_2.1.1.bb
[…]
Thanks again,
Paul
PS: For the future you should try to move to OE-core [1] and meta-oe
where at leaste OE-core gets more support.
[1]
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=9e1aa4d02aed8ade9bbbc60ccab4aa58fe1bd2fd
[2] http://openembedded.org/index.php?title=OpenEmbedded-Core
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Wiki: Interwiki links from at least main page incorrect
Dear Wiki admins, clicking for example on Mailing lists on the main page [1] of our Wiki, instead of [2] it points to [3] which is not available. Since the main page has not been changed, I guess something else in the installation is not working. Thanks, Paul [1] http://openembedded.org/index.php?title=Main_Page [2] http://openembedded.org/index.php?title=Mailing_lists [3] http://openembedded.org/wiki/Mailing_lists signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v3] libroxml: Add version 2.1.1
Dear Tristan,
thank you for your patience.
Am Mittwoch, den 21.09.2011, 14:40 +0200 schrieb Tristan Lelong:
libroxml is a small fast and powerful xml library
build successfully using org.openembedded.dev with DISTRO=minimal and MACHINE
= i686-generic
build successfully using org.openembedded.dev with DISTRO=minimal and MACHINE
= ppce500v2
tested using projects unit tests on powerpc binaries
Signed-off-by: Tristan Lelong tristan.lel...@blunderer.org
---
recipes/libroxml/libroxml.inc | 21 +
recipes/libroxml/libroxml_2.1.1.bb |5 +
2 files changed, 26 insertions(+), 0 deletions(-)
create mode 100644 recipes/libroxml/libroxml.inc
create mode 100644 recipes/libroxml/libroxml_2.1.1.bb
diff --git a/recipes/libroxml/libroxml.inc b/recipes/libroxml/libroxml.inc
new file mode 100644
index 000..eed21d1
--- /dev/null
+++ b/recipes/libroxml/libroxml.inc
@@ -0,0 +1,21 @@
+DESCRIPTION = Small, fast and powerful xml library
+AUTHOR = Tristan Lelong tristan.lel...@libroxml.net
+HOMEPAGE = http://www.libroxml.net;
+SECTION = libs
+PRIORITY = optional
+LICENSE = LGPL
I checked again. This should be `LGPLv2.1+`, I think.
+INC_PR = r1
Please start with `r0` when submitting recipes.
+
+SRC_URI = http://libroxml.googlecode.com/files/${P}.tar.gz;
+
+do_install() {
+ install -D -m 755 ${S}/roxml ${D}/${bindir}/roxml
+ install -D -m 755 ${S}/libroxml.so.0 ${D}/${libdir}/libroxml.so.0
+ install -D -m 644 ${S}/inc/roxml.h ${D}/${includedir}/roxml.h
+ ln -s /usr/lib/libroxml.so.0 ${D}/${libdir}/libroxml.so
+}
+
+PACKAGES = ${PN} ${PN}-dev roxml
Is that intended? Using `=` you override the variable and for example no
debug package is created and the following files are not packaged.
WARNING: the following files were installed but not shipped in any
package:
WARNING: /usr/lib/.debug/libroxml.so.0
WARNING: /usr/bin/.debug/roxml
+FILES_${PN} = ${libdir}/libroxml.so.0
+FILES_${PN}-dev = ${libdir}/libroxml.so ${includedir}/roxml.h
+FILES_roxml = ${bindir}/roxml
Does
PACKAGES += roxml
FILES_roxml = ${bindir}/roxml
work for? I do not know if it is done automatically. Maybe you also have
to add `roxml-dbg` then. I am not sure.
diff --git a/recipes/libroxml/libroxml_2.1.1.bb
b/recipes/libroxml/libroxml_2.1.1.bb
new file mode 100644
index 000..0852930
--- /dev/null
+++ b/recipes/libroxml/libroxml_2.1.1.bb
@@ -0,0 +1,5 @@
+require libroxml.inc
+PR = ${INC_PR}.1
Please also start with 0.
+
+SRC_URI[md5sum] = dc8342d0490bff5a507dbf1de3426102
+SRC_URI[sha256sum] =
e4e91b610614d6cb1204ac9abbb417368fe84654c7de58134b436cfd00f1a244
Thank you! I guess the next iteration will be ready to be committed.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] ti_cgt_c6000_6.1.17_setup_linux_x86.bin error while installing ti-codec-engine
Dear Ibrahim, Am Mittwoch, den 21.09.2011, 07:37 -0700 schrieb ibrahim demir: i have a problem at installing ti codec engine: http://pastebin.com/uU7etDYs . i downloaded ti_cgt_c6000_6.1.17_setup_linux_x86.bin and generated it's md5. in recipes/ti/...6.1.17.bb says md5 is : 41ee41cc74800b06705804f7ef901447. But when i calculate its md5, i get this: 5ee5c8e573ab0a1ba1249511d4a06c27. I download again and again but the result of md5 was the same. Then i changed bb file to 5ee5c8e573ab0a1ba1249511d4a06c27. and run bitbake ti-codec-engine, but the result was: http://pastebin.com/1SCrtWvQ please paste the relevant parts of the output into the message, so that nobody has to open a Web browser for that. You also miss what repository you are using, what distribution and machine! I told you on IRC to be elaborate. If your mail message is smaller than the lines you wrote to the channel you have done something wrong. so in this case what is my problem, what should i do? Thanks, Paul PS: You should also think about using an email program like Mozilla Thunderbird, Mutt or Evolution and not the Web interface. Following the netiquette will be easier then. signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2] libroxml: Add version 2.1.0
Dear Tristan, Am Dienstag, den 20.09.2011, 16:35 +0200 schrieb Tristan Lelong: I corrected the other problems with my recipe and I'm about to submit it again. great! Thank you for following up! There is only one point I don't understand: Please add how you tested this package with. What do you mean by tested? you want the openembedded distro, toolchain, version (git hash)? the full local.conf? the software internal tests? anything else? The distribution and the machine should be fine. Additionally a note that you run tested this by using the tests is enough. […] Thanks, Paul PS: If you top post you do not need to cite anything. Otherwise normally interleaved style is used among free software projects [1]. [1] http://en.opensuse.org/openSUSE:Mailing_list_netiquette signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2] libroxml: Add version 2.1.0
Dear Tristan,
thank you for updating the patch.
Am Mittwoch, den 14.09.2011, 17:00 +0200 schrieb tristan.lel...@blunderer.org:
From: Tristan Lelong tristan.lel...@blunderer.org
libroxml is a small fast and powerful xml library
Please add how you tested this package with.
Signed-off-by: Tristan Lelong tristan.lel...@blunderer.org
---
recipes/libroxml/libroxml.inc | 19 +++
recipes/libroxml/libroxml_2.1.0.bb |6 ++
2 files changed, 25 insertions(+), 0 deletions(-)
create mode 100644 recipes/libroxml/libroxml.inc
create mode 100644 recipes/libroxml/libroxml_2.1.0.bb
diff --git a/recipes/libroxml/libroxml.inc b/recipes/libroxml/libroxml.inc
new file mode 100644
index 000..06322fe
--- /dev/null
+++ b/recipes/libroxml/libroxml.inc
@@ -0,0 +1,19 @@
+DESCRIPTION = Small, fast and powerful xml library
+AUTHOR = Tristan Lelong tristan.lel...@libroxml.net
+HOMEPAGE = http://www.libroxml.net;
+SECTION = libs
+PRIORITY = optional
+INC_PR = r0
+LICENSE = LGPL
Please order according to the style guide [1].
Additionally checking the license this contradicts itself. `LGPL.txt`
actually says version 3 or later, but the header in the the source files
like `roxml.c` says LGPL 2.1 or later.
Please clarify that in the source as you are the upstream author.
Additionally please never release a new source archive without changing
the version number. This causes problems when checksums are used as in
OE.
+
+SRC_URI = http://libroxml.googlecode.com/files/libroxml-2.1.0.tar.gz;
Please use `${P}` instead of `libroxml-2.1.0`.
+
+inherit pkgconfig
You do not ship any pkg-config file.
+
+do_install() {
+oe_runmake install DESTDIR=${D}
+}
+
+PACKAGES= ${PN} roxml
+FILES_${PN} = ${libdir}/libroxml.so.0
+FILES_roxml = ${bindir}/roxml
Why do you need to define that manually?
NOTE: package libroxml-2.1.0-r0.0: task do_qa_staging: Started
WARNING: the following files were installed but not shipped in any
package:
WARNING: /usr/lib/libroxml.so
WARNING: /usr/lib/libroxml.a
WARNING: /usr/lib/pkgconfig/libroxml.pc
WARNING: /usr/lib/.debug/libroxml.so.0
WARNING: /usr/include/roxml.h
WARNING: /usr/share/man/man1/roxml.1
WARNING: /usr/share/doc/libroxml/LGPL.txt
WARNING: /usr/bin/.debug/roxml
diff --git a/recipes/libroxml/libroxml_2.1.0.bb
b/recipes/libroxml/libroxml_2.1.0.bb
new file mode 100644
index 000..b3669e1
--- /dev/null
+++ b/recipes/libroxml/libroxml_2.1.0.bb
@@ -0,0 +1,6 @@
+PR = ${INC_PR}.0
+
+SRC_URI[md5sum] = ad1903efa241914baec2fd432a176549
+SRC_URI[sha256sum] =
bf2d908c330e28e5470fe9a841438b78025dc1406742fc54aad6fa8db401229a
+
+require libroxml.inc
I think `require libroxml.inc` should go to the beginning.
Thanks,
Paul
[1] http://openembedded.org/index.php?title=Styleguide
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v4] linux-libc-headers 2.6.24: backport arm/asm/hwcap.h from recent kernel
Dear Steffen, unfortunately I still have something to add. :( Am Donnerstag, den 15.09.2011, 09:55 +0200 schrieb Steffen Sledz: 1. Please do not use `recent` but write the correct version. In this case it would be 2.6.26 (see below). Enables building of OpenJDK which uses HWCAP_THUMBEE that is not present in 2.6.24 headers and was introduced with commit 4baa9922430662431231ac637adedddbb0cfb2d7 Author: Russell King r...@dyn-67.arm.linux.org.uk Date: Sat Aug 2 10:55:55 2008 +0100 [ARM] move include/asm-arm to arch/arm/include/asm 2. Of course that is not correct and I asked that in my last response why a move should introduce new code lines. Using git log --follow 4baa9922430662431231ac637adedddbb0cfb2d7 -- arch/arm/include/asm/hwcap.h I found the following commit commit d7f864be8323e5394040e2877594645b0e7da85d Author: Catalin Marinas catalin.mari...@arm.com Date: Fri Apr 18 22:43:06 2008 +0100 ARMv7: Add support for the ThumbEE state saving/restoring This patch adds the detection and handling of the ThumbEE extension on ARMv7 CPUs. Signed-off-by: Catalin Marinas catalin.mari...@arm.com introduced in 2.6.26. $ git describe --contains d7f864be8323e5394040e2877594645b0e7da85d v2.6.26-rc1~1090^2~27 Please note that this commit contains not only the addition of HWCAP_THUMBEE to the header but a lot more. So is OpenJDK doing something incorrectly then? Does it detect the wrong architecture? Signed-off-by: Steffen Sledz sl...@dresearch-fe.de Reviewed-by: Paul Menzel paulepan...@users.sourceforge.net --- .../arm-hwcap-add-new-entries.patch| 26 .../linux-libc-headers_2.6.24.bb |6 +++- 2 files changed, 30 insertions(+), 2 deletions(-) create mode 100644 recipes/linux-libc-headers/linux-libc-headers-2.6.24/arm-hwcap-add-new-entries.patch […] Please update the relevant parts and send it to the list again. You can commit it the next day if nobody else objects. Thanks, Paul PS: It is hard for reviewers to see what changed in your patch iterations. For example between v3 and v4. Please add a short note below the commit message and separate that with an additional `---`. `git am` will not pick that comment up then. signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2] eglibc-2.9: allow building with newer GNU make
Am Mittwoch, den 14.09.2011, 16:55 +0200 schrieb Steffen Sledz: Please amend the commit before pushing to replace »newer« with »= 3.82« and the typo below. GNU make = 3.82 does not allow mixed implicit and normal rules Signed-off-by: Steffen Sledz sl...@dresearch-fe.de Acked-by: Khem Raj raj.k...@gmail.com --- recipes/eglibc/eglibc-2.9/make-3.82.patch | 27 +++ recipes/eglibc/eglibc_2.9.bb |3 ++- 2 files changed, 29 insertions(+), 1 deletions(-) create mode 100644 recipes/eglibc/eglibc-2.9/make-3.82.patch diff --git a/recipes/eglibc/eglibc-2.9/make-3.82.patch b/recipes/eglibc/eglibc-2.9/make-3.82.patch new file mode 100644 index 000..64cb270 --- /dev/null +++ b/recipes/eglibc/eglibc-2.9/make-3.82.patch @@ -0,0 +1,27 @@ +eglibc-2.9: allow building with newer GNU make + +GNU make = 3.82 does not allow mixed implicit and normal rules + +Because eglibc-2.9 is superseeded by newer versions it makes no sense s/superseeded/superseded/ (I always make the same mistake.) +to submit this patch upstream. + +Upstream-Status: Inappropriate [other] + +Signed-off-by: Steffen Sledz sl...@dresearch-fe.de + +diff -Nurd libc.orig//manual/Makefile libc/manual/Makefile +--- libc.orig//manual/Makefile 2011-09-13 14:49:57.428424088 +0200 libc/manual/Makefile 2011-09-13 14:50:47.009620484 +0200 Acked-by: Paul Menzel paulepan...@users.sourceforge.net Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2 1/2] Add linux kernel recipe for picoSAM9G45 board
Am Donnerstag, den 15.09.2011, 12:12 +0300 schrieb Nicu Pavel:
Add linux kernel recipe for picoSAM9G45 board[1]. This kernel is based on
stock 2.6.32 with AT91 patches[2], Android patches[3] and board specific
patches.
Some of the board specific patches had been submited upstream[4].Custom
android
related patches won't be submited upstream. Future updates are planned to
include
patches from Android[3] and AT91 Linux tree[5].
1. http://www.mini-box.com/pico-SAM9G45-X
2. http://www.at91.com/linux4sam/bin/view/Linux4SAM/LinuxKernel
3. https://github.com/android/kernel_common
4. http://www.arm.linux.org.uk/developer/patches/search.php?summary=AT91
5. https://github.com/at91linux/linux-2.6-at91
Signed-off-by: Nicu Pavel npa...@mini-box.com
---
recipes/linux/picosam9/defconfig | 1806
++
recipes/linux/picosam9_git.bb| 32 +
2 files changed, 1838 insertions(+), 0 deletions(-)
create mode 100644 recipes/linux/picosam9/defconfig
create mode 100644 recipes/linux/picosam9_git.bb
[…]
diff --git a/recipes/linux/picosam9_git.bb b/recipes/linux/picosam9_git.bb
new file mode 100644
index 000..892c93d
--- /dev/null
+++ b/recipes/linux/picosam9_git.bb
@@ -0,0 +1,32 @@
+DESCRIPTION = Kernel for picoSAM9 board
(http://www.mini-box.com/pico-SAM9G45-X)
+HOMEPAGE = http://arm.mini-box.com;
+KV = 2.6.32
+SRCREV = 5d564f090ee99a0570a2cc912ebc30b65922f7bb
+PV = ${KV}+gitr${SRCREV}
+PR = r0
+
+require linux.inc
+
+# For Angstrom and Android Eclair (for a Android Gingerbread compatible
kernel use
+# branch=minibox-picopc-2.6.32-gingerbread)
+SRC_URI = \
+
git://gitorious.org/picopc-kernel/kernel.git;protocol=git;branch=minibox-picopc-2.6.32
\
+ file://defconfig \
+
+
+S = ${WORKDIR}/git
+
+COMPATIBLE_HOST = arm.*-linux
+COMPATIBLE_MACHINE = picosam9
+# mem=128M@ - picoSAM9 has 2x128Mb memory banks at different adresses
and uses
ad*d*resses
+# sparsemem memory model to use both banks
+# rootwait=1 - wait for the root device to show up (picosam9 boots from
microSD(MMC))
+# rootdelay=1 - wait 1 second before mounting the root fs (some delay exists
between
+# root device showing up and partition detection).
+# androidboot.hardware=picopc - compatibility option for booting android
+# (loading of init.picopc.rc and libhardware
libs)
+# init=/init - compatibility option for starting android init.If not found
standard /linuxrc is
+# executed
+CMDLINE = mem=128M@0x2000 mem=128M@0x7000 console=ttyS0,115200
root=/dev/mmcblk0p2 rw init=/init rootdelay=1 rootwait=1 loglevel=7
androidboot.hardware=picopc
Is the increased(?) loglevel needed?
+KERNEL_IMAGETYPE = uImage
+ARM_KEEP_OABI = 1
I will push this patch with the typo corrected. You do not need to
resend it.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH v2 2/2] Add machine configuration for picoSAM9G45 board
Am Donnerstag, den 15.09.2011, 12:12 +0300 schrieb Nicu Pavel: Add machine configuration for picoSAM9G45 board[1]. More information about this board and software support can be found at [2]. 1. http://www.mini-box.com/pico-SAM9G45-X 2. http://arm.mini-box.com/index.php?title=Main_Page Signed-off-by: Nicu Pavel npa...@mini-box.com --- conf/machine/picosam9.conf | 17 + 1 files changed, 17 insertions(+), 0 deletions(-) create mode 100644 conf/machine/picosam9.conf diff --git a/conf/machine/picosam9.conf b/conf/machine/picosam9.conf new file mode 100644 index 000..3d75627 --- /dev/null +++ b/conf/machine/picosam9.conf @@ -0,0 +1,17 @@ +#@TYPE: Machine +#@Name: pico-SAM9G45 (http://www.mini-box.com/pico-SAM9G45-X) +#@DESCRIPTION: Machine configuration for the picoSAM9G45 board with a at91sam9g45 processor + +# More information can be found here: +# http://arm.mini-box.com/index.php?title=Compiling_Angstrom_for_pico-SAM9G45 +# Images tested: base-image and x11-image … with `angstrom-2010.x` I guess. + +TARGET_ARCH = arm + +PREFERRED_PROVIDER_virtual/kernel = picosam9 + +PREFERRED_PROVIDER_xserver = xserver-kdrive + +MACHINE_FEATURES += usbhost kernel26 apm vfat screen touchscreen ethernet wifi bluetooth + +require conf/machine/include/tune-arm926ejs.inc Acked-by: Paul Menzel paulepan...@users.sourceforge.net I will commit your patches tomorrow if nobody has any objections. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] Add support for mini-box.com picoSAM9G45 board
Dear Nicu, Am Donnerstag, den 15.09.2011, 12:15 +0300 schrieb Nicu Pavel: On Wed, Sep 14, 2011 at 1:13 PM, Paul Menzel wrote: [...] Please resend with these comments addressed as [PATCH v2] [4]. Thanks for your comments, I resent the patches per your instructions. thank you very much for addressing my comments. It is much appreciated. As Otavia pointed out, you should consider moving to oe-core and meta-oe in the future. meta-oe lacks some recipes available in oe.dev (oe-classic) but it is actively developed and gets more testing and security support. For some reason registering on patchwork, gives me and error and I don't receive the activation email, so I'm unable to update the status of the previous patch. Several people have reported problems with Patchwork. I hope an admin will look into it. Thanks, Paul [1] http://openembedded.org/index.php?title=OpenEmbedded-Core signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] meta-oe: Patch review/quality and new and new commit policy
Dear OE folks, looking at the commit log of meta-oe, I see two issues. 1. A lot of these patches were never sent to *this* list like [2]. 2. The commit message are not adhering to the guide lines [1] and are therefore not as useful as they could be. If I remember correctly one reason for the new structure was to also improve the quality of OpenEmbedded. And as there is nobody having any time to update documentation commit messages are the only means right now to document things correctly. I know that a lot of you are probably annoyed by me saying guide lines, guide lines, guide lines all over again, but I have not seen any other suggestions yet and looking at the current meta-oe state I doubt that the quality is that much better than before. The only benefit I can see is that there are not so many versions of the same recipe. Since nobody else did so already I propose the following policy to get patches into meta-oe. They should be in effect immediately and can be improved/adapted over time. 1. Commits have to adhere to the Commit Patch Message Guidelines. 2. It is advisable to add to the commit message how the patch was tested (build, run time, build system, distribution, machine). 3. Patches have to be send for review (preferably with a pull request) to openembedded-devel. After one week without any objections they can be pulled into the repository. 4. The state in the patch queue Patchwork¹ has to be updated. Thanks, Paul ¹ As soon as it works correctly again. [1] http://openembedded.org/index.php?title=Commit_Patch_Message_Guidelines [2] http://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg08136.html signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] How to call the old repository: oe.dev or OE classic?
Dear OE folk, it is confusing for outsiders if oe.dev and OE classic are referring to the same repository or not. So we need to make up an official name for the old repository. oe.dev or OE classic? I favor oe.dev, because it is shorter Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Patchwork issues
Dear Git and Patchwork admins, could you please look into the following issues. 1. People report, that they cannot register to Patchwork because their username is already registered. But they have never registered before. (Reported on the list and on IRC.) 2. I am not allowed to update the state of other people patches. Could you give people this right automatically if they are OE devs (have commit access – not feasible any more with the new structure?) or grant them these right after they have been registered for a months or so or reply to a certain message? 3. Could you please install the example hooks of Patchwork to automatically update the patch state when it is committed. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] qwt: import from openembedded.dev
Dear Denis,
thank you for the patch. Please remember to tag patches for meta-oe with
[meta-oe].
Am Donnerstag, den 15.09.2011, 11:42 +0200 schrieb Denis Carikli:
The only change between openembedded.dev and meta-openembedded was
the addition of LIC_FILES_CHKSUM
Signed-off-by: Denis Carikli de...@eukrea.com
I would prefer if you format such import commits as follows.
qwt: Add version 5.2.1 (initial recipe)
• Import recipe from OE-classic [1].
• Add `LIC_FILES_CHKSUM`.
• Build and run tested with ….
[1]
http://git.openembedded.org/cgit.cgi/openembedded/tree/recipes/qwt/?id=750e869586413347cc73de1615979288af750c97
What URL or commit ID to use is up to you.
---
meta-oe/recipes-qt/qwt/qwt-e_5.2.1.bb |8
meta-oe/recipes-qt/qwt/qwt.inc| 33
+
meta-oe/recipes-qt/qwt/qwt_5.2.1.bb |8
3 files changed, 49 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-qt/qwt/qwt-e_5.2.1.bb
create mode 100644 meta-oe/recipes-qt/qwt/qwt.inc
create mode 100644 meta-oe/recipes-qt/qwt/qwt_5.2.1.bb
diff --git a/meta-oe/recipes-qt/qwt/qwt-e_5.2.1.bb
b/meta-oe/recipes-qt/qwt/qwt-e_5.2.1.bb
new file mode 100644
index 000..2f55061
--- /dev/null
+++ b/meta-oe/recipes-qt/qwt/qwt-e_5.2.1.bb
@@ -0,0 +1,8 @@
+inherit qt4e
+
+require qwt.inc
+
+SRC_URI[qwt.md5sum] = 4a595b8db0ec3856b117836c1d60cb27
+SRC_URI[qwt.sha256sum] =
e2b8bb755404cb3dc99e61f3e2d7262152193488f5fbe88524eb698e11ac569f
+
+RPROVIDES_${PN}-dev = libqwt-dev
\ No newline at end of file
Should these new lines be added?
diff --git a/meta-oe/recipes-qt/qwt/qwt.inc b/meta-oe/recipes-qt/qwt/qwt.inc
new file mode 100644
index 000..da1ed11
--- /dev/null
+++ b/meta-oe/recipes-qt/qwt/qwt.inc
@@ -0,0 +1,33 @@
+DESCRIPTION = Qt Widget Extension for Technical Applications
+SECTION = libs
+PRIORITY = optional
+
+# LGPLv2.1 + some exceptions
+LICENSE = QWTv1.0
+LIC_FILES_CHKSUM = file://COPYING;md5=dac2743472b0462ff3cfb4af42051c88
+
+SRC_URI = ${SOURCEFORGE_MIRROR}/qwt/qwt-${PV}.tar.bz2;name=qwt
+
+S = ${WORKDIR}/qwt-${PV}
Is this the default? If yes please remove it?
+
+do_configure_prepend() {
+ sed -i -e 's:RELEASE_SUFFIX = :RELEASE_SUFFIX =
${QT_LIBINFIX}:' *.pri
+ sed -i -e s:lqwt:lqwt${QT_LIBINFIX}:g -e
s:/usr/local/qwt-$\${QwtVersion}:${prefix}:g *.prf
+ sed -e 's/#CONFIG += QwtExamples/CONFIG += QwtExamples/g' -i
qwtconfig.pri
+ sed -i -e s:/usr/local/qwt-${PV}:${D}${prefix}:g ${S}/*.pri
+}
+
+do_install() {
+ oe_runmake -e install
+ install -d ${D}${datadir}/doc/${PN}
+ mv ${D}${prefix}/doc/* ${D}${datadir}/doc/${PN}/
+ cd ${S}/examples
+ install -d ${D}/${bindir}
+ cd bin${QT_LIBINFIX}/
+ for i in * ; do
+ cp -pPR ${i} ${D}/${bindir}/${i}${QT_LIBINFIX}
+ done
+}
+
+PACKAGES_prepend = ${PN}-examples
+FILES_${PN}-examples = ${bindir}/*
diff --git a/meta-oe/recipes-qt/qwt/qwt_5.2.1.bb
b/meta-oe/recipes-qt/qwt/qwt_5.2.1.bb
new file mode 100644
index 000..238a4fb
--- /dev/null
+++ b/meta-oe/recipes-qt/qwt/qwt_5.2.1.bb
@@ -0,0 +1,8 @@
+inherit qt4x11
+
+require qwt.inc
+
+SRC_URI[qwt.md5sum] = 4a595b8db0ec3856b117836c1d60cb27
+SRC_URI[qwt.sha256sum] =
e2b8bb755404cb3dc99e61f3e2d7262152193488f5fbe88524eb698e11ac569f
+
+RPROVIDES_${PN}-dev = libqwt-dev
\ No newline at end of file
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
