From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: I've downloaded oe
Date: Wed, 24 Nov 2010 09:07:07 +0100 [thread overview]
Message-ID: <20101124080705.GF3274@jama> (raw)
In-Reply-To: <AANLkTimymQB4kxvp-ybAzpUMMxQNy43GZyxKNzmRH3Uw@mail.gmail.com>
On Wed, Nov 24, 2010 at 08:52:41AM +0100, Frans Meulenbroeks wrote:
> What about moving all recipes that do not fetch and also did not fetch
> during Martins test from last march/april to a directory non-fetching
> or so?
But those recipes were only those where I wasn't able to find the source
at all (even with google help and couple of popular premirrors). Any
origin for source was fine for me, because I was only interested in
checksum check.
> Apparently these are non fetchable for a long time, with no one
> apparently building them or having an interest to fix them.
More likely those who were building those before are still building
OK, because they had it in theirs downloads dir. (but the second part is
right :/).
> My proposal would be to do that before the release is made, thereby
> improving the % of the recipes that build.
We can improve it also by putting those missing upstream files to
sources.openembedded.org and use it as premirror. But first we hav to
find someone who still have it in downloads dir :/ (I don't).
Removing recipes would need to remove those also from tasks/images and
in the end release images could miss some important functionaly in worst
case.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-11-24 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 20:03 I've downloaded oe Klaus Schwarzkopf
2010-11-23 20:19 ` Khem Raj
2010-11-24 7:52 ` Frans Meulenbroeks
2010-11-24 8:07 ` Martin Jansa [this message]
2010-11-24 9:18 ` Frans Meulenbroeks
2010-11-25 12:07 ` Klaus Schwarzkopf
2010-11-25 12:44 ` Frans Meulenbroeks
2010-11-25 13:01 ` Martin Jansa
2010-11-25 11:58 ` Klaus Schwarzkopf
2010-11-25 12:43 ` Frans Meulenbroeks
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=20101124080705.GF3274@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.