From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Stable source repository
Date: Tue, 22 Jul 2008 13:56:22 +0200 [thread overview]
Message-ID: <g64ht6$h2u$1@ger.gmane.org> (raw)
In-Reply-To: <d2b9ea600807220111i4c3adc1ekcb470034329e18f7@mail.gmail.com>
Esben Haabendal wrote:
> Hi
>
> For some reason, some OSS projects does not offer persistent access to
> old releases,
> which continously give problems for OE and other similar distributions.
Angstrom already provides a sourcemirror for exactly this reason.
>
> With the org.openembedded.stable branch, this problem is considerably worse.
> The usual fix in .dev is to upgrade the recipes to a current release,
> which of-course
> is not what we want for a stable branch.
>
> Take for example
> http://bugs.openembedded.net/show_bug.cgi?id=4227
Fakeroot is present on the angstrom sourcemirror.
> I think it is worth considering a permanent solution to this kind of problems.
> We should have a download server which carries all sources referred to
> by http and ftp URI's in org.openembedded.stable recipes.
> Why not setup ftp://downloads.openembedded.org/org.openmbedded.stable
> to mirror a copy of all sources referred to by current .stable recipes, and
> when a bug is filed with a missing source, the solution is simply to change
> the SRC_URI to use the ftp://downloads.openembedded.org URI instead.
>
> Of-course, unless continous manual labor is to be required, we need to
> write a script or something like that to maintain the mirror repository.
The angstrom autobuilder updates the sourcemirror already with
distributable sources.
> And we need a server with enough storage and a big fat pipe to the
> Internet.
>
> What do you think?
If you use a sane distro like angstrom, you will automagically have a
source mirror.
regards,
Koen
next prev parent reply other threads:[~2008-07-22 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 8:11 Stable source repository Esben Haabendal
2008-07-22 8:34 ` Javi Roman
2008-07-22 8:45 ` Leon Woestenberg
2008-07-22 21:07 ` Esben Haabendal
2008-07-30 15:07 ` Leon Woestenberg
2008-07-30 15:30 ` Leon Woestenberg
2008-07-22 11:56 ` Koen Kooi [this message]
2008-07-22 21:14 ` Esben Haabendal
2008-07-22 19:05 ` Rich Pixley
2008-07-22 19:28 ` Philip Balister
2008-07-22 21:17 ` Esben Haabendal
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='g64ht6$h2u$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.