From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [help] openembedded tarball sources on HTTP
Date: Mon, 26 Oct 2009 13:19:39 +0000 [thread overview]
Message-ID: <1256563179.23985.13.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <ec1f3d400910260325i54971290u914ff2c0a6ca301d@mail.gmail.com>
I don't think anybody is publishing a comprehensive set of SCM-derived
source tarballs. As you say below, oesources.org was the closest to
this but, since its demise, I don't think anybody else has stepped
forwards to fill the vacancy. Some individual DISTROs do mirror the
sources that they are using, and you might like to check whether your
distro falls into that category, but I don't believe there is any
cross-distribution source mirror at present.
Indeed, mirroring a full set of tarballs for every conceivable
SRCDATE/SRCREV would be a somewhat daunting undertaking: a more feasible
option would probably be to do an svn-over-http kind of proxy thing,
where a request for something like
http://svnproxy.oe.org/checkout?uri=svn://eleet.org/repository&rev=1234
would run the checkout in real time and hand you back a tarball. If you
wanted to implement such a thing then it might be feasible to get it
hosted on one of the oe.org machines.
However, most/all recipes do offer at least one released tarball which
you should be able to use rather than checking out from SCM every time.
If you find a particular package whose sources are simply not available
any other way than CVS or SVN then post the details here and someone may
be able to point you at a tarball.
p.
On Mon, 2009-10-26 at 15:55 +0530, RK Raggit wrote:
> anyone with some idea on this .. ? sorry for pushing , but i am kind of
> evaluating OE and would like to know whether this is possible at all ?
>
> ...unblocking cvs,svn ports is defnitely not an option for me.
>
> --RK
>
> On Fri, Oct 23, 2009 at 4:51 PM, RK Raggit <rk.raggit@gmail.com> wrote:
>
> > Hi there,
> >
> > I am building openembedded recipes but i am behind a proxy that only allows
> > http accesses and blocks cvs,svn ports.
> >
> > I would like to know where i can obtain pristine OE package (tarball)
> > sources from a HTTP link. I tried
> >
> > http://oesources.org/source/current
> >
> > ...but that link does not work. Could someone please guide me the correct
> > link ? I will update my CVS_TARBALL_STASH
> > variable with this link.
> >
> > Thanks
> > RK
> >
> >
> >
> _______________________________________________
> 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:[~2009-10-26 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 11:21 [help] openembedded tarball sources on HTTP RK Raggit
2009-10-26 10:25 ` RK Raggit
2009-10-26 10:44 ` Holger Hans Peter Freyther
2009-10-26 17:49 ` GNUtoo
2009-10-26 12:25 ` Philip Balister
2009-10-26 12:49 ` Koen Kooi
2009-10-26 13:19 ` Phil Blundell [this message]
2009-10-27 11:53 ` RK Raggit
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=1256563179.23985.13.camel@mill.internal.reciva.com \
--to=pb@reciva.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.