From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] Preferring tar.bz2 over tar.gz if there's a choice
Date: Sat, 21 Oct 2006 00:33:31 +0300 [thread overview]
Message-ID: <595433076.20061021003331@gmail.com> (raw)
Hello openembedded-devel,
Nowadays, with multimegabyte software downloads, many projects
provide both tar.bz2 and tar.gz archives for downloads. I'd like to
make a proposal that we prefer tar.bz2 over .gz for obvious reason of
saving bandwidth and disk space for lots of people using OE. In
particular, I'd like to propose that it's ok to change .gz to .bz2 if
such case is spotted.
We should be reasonably safe with this, as gzip can be considered
pretty well a legacy archiver for big downloads now. The projects
which started use bzip2 hardly give it up. And of course, many
projects alreday use bzip2 solely, so it's not like adding a new
dependency for OE.
Specifically, I have such patches for gdb_6.4 and libxml2_2.6.26 now
in my tree.
(One would ask - why do I care up to the level of patchuing existing
recipes? I'm exactly one of bandwidth-challenged, so try to use cheap
local mirrors, and the mirrors of course usually have .bz2. I checked
taht upstream actually provides .bz2, of course.)
--
Best regards,
Paul mailto:pmiscml@gmail.com
next reply other threads:[~2006-10-20 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 21:33 Paul Sokolovsky [this message]
2006-10-20 21:57 ` [RFC] Preferring tar.bz2 over tar.gz if there's a choice Richard Purdie
2006-10-20 21:58 ` Justin Patrin
2006-10-20 22:39 ` Richard Purdie
2006-10-21 0:41 ` Justin Patrin
2006-10-21 1:09 ` Paul Sokolovsky
2006-10-20 22:23 ` Michael 'Mickey' Lauer
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=595433076.20061021003331@gmail.com \
--to=pmiscml@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.