From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [help] openembedded tarball sources on HTTP
Date: Mon, 26 Oct 2009 08:25:18 -0400 [thread overview]
Message-ID: <4AE5952E.7060601@balister.org> (raw)
In-Reply-To: <ec1f3d400910260325i54971290u914ff2c0a6ca301d@mail.gmail.com>
On 10/26/2009 06:25 AM, 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.
One possible business associated with OE would be maintaining a server
accessible via http that collected all the needed sources and mae them
available to people with difficult firewall situations. I'm not sure how
to market such a thing though.
Philip
>
> --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 12:26 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 [this message]
2009-10-26 12:49 ` Koen Kooi
2009-10-26 13:19 ` Phil Blundell
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=4AE5952E.7060601@balister.org \
--to=philip@balister.org \
--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.