From: butters <butters@station51.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Broken recipes
Date: Sun, 30 May 2010 15:23:38 +0200 [thread overview]
Message-ID: <4C0266DA.6050709@station51.net> (raw)
In-Reply-To: <91EED1BF-B355-4D13-ACDC-4A6F8AA79897@vanille-media.de>
I think I just did mention some packages... Maemo is missing "outo"
during the initial stages of checking for all available recipes and
tasks and it's missing things. This is the same thing with the
task-openmoko.bb ...
I'm compiling for the mini2440 board. It's an armv4t board. The majority
of the things that I can see will and should compile for it. But when I
say broken, I am talking about recipes that don't even make it to
running the queue part... the recipes that stop before that because of
missing components. I understand that certain packages might not compile
for obscure hardware.
As I said in my previous post, I think that more people get confused and
waste a lot of time trying to fix broken things. From what I understand
of Maemo, not all of it is available as open source so it shouldnt be
included at all, right???
I've not tried to build everything. So I don't have a list. I'm just
mentioning two that I tried today, and that I've tried over the past few
months with the same results.
Thanks for your reply :)
Bill
On 5/30/2010 3:14 PM, Dr. Michael Lauer wrote:
> Hi Bill,
>
>
>> Can someone tell me the reason for keeping broken recipes in the tree?
>>
> Define 'broken'; some packages only build for a certain combination of $MACHINE and $DISTRO,
> and sometimes perhaps even $OUT_OF_TREE_OVERLAY.
>
> If a package is definitely broken, we should move it to 'broken' (if there is still
> any interest in it), or remove it altogether. Most of the time it's maintainers disappearing
> and who knows when or if they will appear again, so why annoy them by removing the recipe?
>
> There's also lack of manpower to throw into the equation.
>
> Which concrete recipes do you mean? I'd agree with removing a dozen of openmoko ones
> for distributions that noone works on any longer (i.e. Openmoko 2007.2 and Openmoko 2008),
> but please tell me exactly which ones.
>
> Cheers,
>
> :M:
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2010-05-30 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 9:37 Faking sign offs is bad Koen Kooi
2010-05-29 10:58 ` Frans Meulenbroeks
2010-05-29 11:14 ` Andrea Adami
2010-05-30 1:30 ` Holger Freyther
2010-05-30 12:51 ` Broken recipes butters
2010-05-30 13:14 ` Dr. Michael Lauer
2010-05-30 13:23 ` butters [this message]
2010-05-29 11:15 ` Faking sign offs is bad Andrea Adami
2010-05-29 17:09 ` Andrea Adami
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0266DA.6050709@station51.net \
--to=butters@station51.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox