Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: sstate compression
Date: Wed, 04 Jan 2012 16:53:23 +0000	[thread overview]
Message-ID: <1325696004.28005.80.camel@phil-desktop> (raw)
In-Reply-To: <1325695637.20759.32.camel@ted>

On Wed, 2012-01-04 at 16:47 +0000, Richard Purdie wrote:
> Just to note that looking for multiple versions can cause a fair bit of
> network traffic as for http:// mirror urls it will have to wget each in
> turn.

True, though I suppose if the fetching was to be moved into python
(rather than an external wget) then it would just be repeated GETs over
a single persistent connection which wouldn't be all that much overhead.
And, even with non-persistent connections, the amount of data involved
in establishing an extra TCP connection and sending a GET is fairly
negligible compared to the size of the download you're going to end up
doing.

>Better would be one file name and dynamic detection of the
>compression format I guess.

Yes, or that.  It's a shame that "tar -a" doesn't have the capability to
determine the compression method using magic numbers instead of the
filename.

p.





  reply	other threads:[~2012-01-04 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 15:05 sstate compression Phil Blundell
2012-01-04 15:33 ` Richard Purdie
2012-01-04 16:31   ` McClintock Matthew-B29882
2012-01-04 16:32     ` Chris Larson
2012-01-04 16:41       ` Phil Blundell
2012-01-04 16:47         ` Richard Purdie
2012-01-04 16:53           ` Phil Blundell [this message]
2012-01-04 16:58             ` Richard Purdie
2012-01-04 16:55           ` McClintock Matthew-B29882

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=1325696004.28005.80.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@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