From: bdharring <bdharring@wisc.edu>
To: gentoo-dev@gentoo.org
Cc: John Whitney <jjw@linuxmail.org>
Subject: Re: [gentoo-dev] GLEP for Deltup package update system
Date: Tue, 29 Jul 2003 04:14:24 -0500 [thread overview]
Message-ID: <0BC06F53-C1A5-11D7-9B6C-00306580AC5C@wisc.edu> (raw)
In-Reply-To: <20030728220925.12596.qmail@linuxmail.org>
On Monday, July 28, 2003, at 05:09 PM, John Whitney wrote:
> All this project needs is the green light. Isn't it about time we
> make Gentoo more available to the bandwidth deprived?
Taking a quick look at deltup-0.4 (most recent available via
sourceforge), it is still reliant on having an older version of bzip2
installed to handle cases where the target distfile was compressed w/
the older version of bzip2. That strikes me as side stepping the
problem- say down the line, either the bzip2 or gzip implementation was
tweaked again to produce a slightly better compression, you'd run into
the same problem again of maintaining md5 correctness.
As I had mentioned in the past on this ml, I'd think some solution
allowing for an md5 checksum of the data rather then the compressed
form of said data would be a better solution. On the plus side, it
could be extended to allow the user better control over what
compression is used on their distfiles, but that's ancillary to the
problem I mentioned above.
Other then that point of contention, kudos on bdelta's performance.
~bdh
> ---JJW
> --
> ______________________________________________
> http://www.linuxmail.org/
> Now with e-mail forwarding for only US$5.95/yr
>
> Powered by Outblaze
>
> --
> gentoo-dev@gentoo.org mailing list
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-29 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 22:09 [gentoo-dev] GLEP for Deltup package update system John Whitney
2003-07-29 9:14 ` bdharring [this message]
2003-07-29 12:20 ` Kurt Lieber
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 16:45 John Whitney
2003-07-30 9:43 ` Paul de Vrieze
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=0BC06F53-C1A5-11D7-9B6C-00306580AC5C@wisc.edu \
--to=bdharring@wisc.edu \
--cc=gentoo-dev@gentoo.org \
--cc=jjw@linuxmail.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