Koen Kooi | 1 Feb 08:29
Gravatar

Re: [oe] [meta-gnome][PATCH 2/2 v2] Add recipe for gnome-mplayer 1.0.5.


Op 31-01-12 23:05, Peter Tworek schreef:
> Run tested on netbookpro.
> 
> Signed-off-by: Peter Tworek <tworaz666 <at> gmail.com> --- 
> .../gnome-mplayer/gnome-mplayer_1.0.5.bb           |   19
> +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-) 
> create mode 100644
> meta-gnome/recipes-apps/gnome-mplayer/gnome-mplayer_1.0.5.bb
> 
> diff --git a/meta-gnome/recipes-apps/gnome-mplayer/gnome-mplayer_1.0.5.bb
> b/meta-gnome/recipes-apps/gnome-mplayer/gnome-mplayer_1.0.5.bb new file
> mode 100644 index 0000000..55e82b5 --- /dev/null +++
> b/meta-gnome/recipes-apps/gnome-mplayer/gnome-mplayer_1.0.5.bb @@ -0,0
> +1,19 @@ +DESCRIPTION = "A GTK+ interface to MPlayer" +HOMEPAGE =
> "http://code.google.com/p/gnome-mplayer" +SECTION = "multimedia" + 
> +LICENSE = "GPLv2" +LIC_FILES_CHKSUM =
> "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552" + +DEPENDS = "gmtk
> gtk+ alsa-lib libnotify glib-2.0 dbus-glib virtual/libx11 libxscrnsaver" 
> +RDEPENDS = "mplayer"

RDEPENDS_${PN} and move it down to its proper place

Paul Menzel | 1 Feb 10:14
Picon

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 <tworaz666 <at> 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 0000000..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"
(Continue reading)

Andreas Müller | 1 Feb 10:01

Re: [oe] [meta-xfce][PATCH v2] Add recipe for xarchiver 0.5.2.

On Tue, Jan 31, 2012 at 8:54 PM, Peter Tworek <tworaz666 <at> gmail.com> wrote:
> Signed-off-by: Peter Tworek <tworaz666 <at> 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 0000000..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"
> +SECTION = "x11"
> +
> +LICENSE = "GPLv2"
> +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"
> --
(Continue reading)

Thilo Fromm | 1 Feb 09:26
Picon

Re: [oe] [meta-java][PATCH] llvm-config: Work around shebang max length issue

Hello Henning,

>> > This patch works around a max shebang length issue
>> > in llvm's llvm-config.
>>
>> Some feedback on the patch would be great.
>>
>
> I am a bit short of time at the moment. So I can not test or apply your patch.
> For the longer term llvm should go to core.
>

Okay. We'll maintain this patch in our HidaV layer (which is
https://github.com/DFE/HidaV) for the time being.

Regards,
Thilo

--

-- 
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228   mailto:fromm <at> dresearch-fe.de
Fax: +49 (30) 515 932 77    http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle

_______________________________________________
Openembedded-devel mailing list
(Continue reading)

Paul Eggleton | 1 Feb 11:07
Picon

Re: [oe] Splitting meta-oe

On Wednesday 25 January 2012 12:48:11 Paul Eggleton wrote:
> The meta-oe layer [1] is becoming the home for additional recipes that we
> miss from OE-Classic that don't have another obvious layer to go into, and
> this is a good thing. However I think that meta-oe is already in a state
> where quite a few people feel the new structure is not working for them.
> 
> As I see it, meta-oe is trying provide the following:
> 
>  1) Additional recipes that are not in OE-Core
> 
>  2) Additional functionality for OE-Core recipes that we can't enable in OE-
> Core itself (e.g. enabling postgres support in Qt) - mostly just a
> side-effect of #1
> 
>  3) A place to preserve old versions of recipes that have been removed from
> OE-Core in favour of newer versions
> 
>  4) Newer less-well tested versions of recipes
> 
> I think what most people want when they enable meta-oe in their layer
> configuration is #1, and it's probably OK to get #2 along with it. They do
> not however expect versions of toolchains, eglibc or other fairly
> fundamental bits and pieces that might cause their build to fail when
> everything worked fine just building with OE-Core (#4). Equally I expect
> there will be some people who want just #3 and nothing else.
> 
> I understand there is significant value in providing all of these things, I
> just think we shouldn't be trying to do them all in one largely indivisible
> layer. In our new layer structure we should be able to find a way to split
> the metadata so that people who want any combination can still have what we
(Continue reading)

Koen Kooi | 1 Feb 11:33
Gravatar

Re: [oe] Splitting meta-oe


Op 1 feb. 2012, om 11:07 heeft Paul Eggleton het volgende geschreven:

> On Wednesday 25 January 2012 12:48:11 Paul Eggleton wrote:
>> The meta-oe layer [1] is becoming the home for additional recipes that we
>> miss from OE-Classic that don't have another obvious layer to go into, and
>> this is a good thing. However I think that meta-oe is already in a state
>> where quite a few people feel the new structure is not working for them.
>> 
>> As I see it, meta-oe is trying provide the following:
>> 
>> 1) Additional recipes that are not in OE-Core
>> 
>> 2) Additional functionality for OE-Core recipes that we can't enable in OE-
>> Core itself (e.g. enabling postgres support in Qt) - mostly just a
>> side-effect of #1
>> 
>> 3) A place to preserve old versions of recipes that have been removed from
>> OE-Core in favour of newer versions
>> 
>> 4) Newer less-well tested versions of recipes
>> 
>> I think what most people want when they enable meta-oe in their layer
>> configuration is #1, and it's probably OK to get #2 along with it. They do
>> not however expect versions of toolchains, eglibc or other fairly
>> fundamental bits and pieces that might cause their build to fail when
>> everything worked fine just building with OE-Core (#4). Equally I expect
>> there will be some people who want just #3 and nothing else.
>> 
>> I understand there is significant value in providing all of these things, I
(Continue reading)

Alex J Lennon | 1 Feb 11:39
Picon
Favicon
Gravatar

Re: [oe] FOSDEM 2012 - stand organization thread

Hi,

Can anybody point me to an SVG graphic for the OpenEmbedded logo to put 
on a tag?

(I'm still happy to print off tags if people wish to contact me, 
although I may not have
time after today)

Regards,

Alex
Picon

[oe] Can't build openembedded: fail in picosam9_git.bb

Hello all!

I've got a problem with building console-image for MACHINE=picosam9. It 
fails while processing picosam9_git.bb with these messages:

> NOTE: Running task 1473 of 3919 (ID: 516, 
> /home/arm/stuff/openembedded/recipes/linux/picosam9_git.bb, do_fetch)
> --2012-02-01 05:17:36--  
>
http://www.angstrom-distribution.org/unstable/sources/git_gitorious.org.picopc-kernel.kernel.git_5d564f090ee99a0570a2cc912ebc30b65922f7bb.tar.gz 
>
> Resolving www.angstrom-distribution.org... NOTE: package 
> picosam9-2.6.32+gitr5d564f090ee99a0570a2cc912ebc30b65922f7bb-r0: task 
> do_fetch: Started
> NOTE: fetch 
>
http://www.angstrom-distribution.org/unstable/sources/git_gitorious.org.picopc-kernel.kernel.git_5d564f090ee99a0570a2cc912ebc30b65922f7bb.tar.gz 
>
> 188.40.83.200
> Connecting to www.angstrom-distribution.org|188.40.83.200|:80... 
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2012-02-01 05:17:37 ERROR 404: Not Found.
>
> Cloning into 
> /home/arm/sources/git/gitorious.org.picopc-kernel.kernel.git...
> fatal: The remote end hung up unexpectedly
> fatal: early EOF
> fatal: index-pack failed
> ERROR: TaskFailed event exception, aborting
(Continue reading)

Otavio Salvador | 1 Feb 12:11
Picon
Gravatar

Re: [oe] Splitting meta-oe

On Wed, Feb 1, 2012 at 08:33, Koen Kooi <koen <at> dominion.thruhere.net> wrote:

> I'm waiting for FOSDEM and ELC to discuss this face to face.

I won't be on those events but I'd like to participate of the discussion so
please use the mailing list.

--

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio <at> ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
Henning Heinold | 1 Feb 13:57
Picon
Picon
Favicon

Re: [oe] [meta-java][PATCH] llvm-config: Work around shebang max length issue

On Wed, Feb 01, 2012 at 09:26:23AM +0100, Thilo Fromm wrote:
> Hello Henning,
> 
> >> > This patch works around a max shebang length issue
> >> > in llvm's llvm-config.
> >>
> >> Some feedback on the patch would be great.
> >>
> >
> > I am a bit short of time at the moment. So I can not test or apply your patch.
> > For the longer term llvm should go to core.
> >
> 
> Okay. We'll maintain this patch in our HidaV layer (which is
> https://github.com/DFE/HidaV) for the time being.
> 
> Regards,
> Thilo

btw. you can make a pull request.

Bye Henning

Gmane