From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GLEP for Deltup package update system
Date: Wed, 30 Jul 2003 11:43:43 +0200 [thread overview]
Message-ID: <200307301143.43384.pauldv@gentoo.org> (raw)
In-Reply-To: <20030729164521.22199.qmail@linuxmail.org>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1194 bytes --]
On Tuesday 29 July 2003 18:45, John Whitney wrote:
> The space requirements are dynamic - they can be scaled to any level
> desired. We don't need patches for every package. This is accomplished by
> knowing which patches are available before trying to download them. You
> can provide a significant number of patches with just 100MB of space. Take
> a look at my demo repository: ftp://sunsite.dk/projects/deltup/patchfiles.
> All these patches take under 50MB and are still not fully optimized (newer
> patches will be about 33% more efficient). It'd be great to start out with
> patches for kernel, kde, gnome, gcc, mozilla, and some other big and
> necessary packages. Remember, there are a lot of dial-up users out there
> (some with only one phone line! :O :) ) A quota based system would be
> fine...
You also might want to use download figures from a used mirror (not the
failsafe that is last in the list) to see which patches are actually wanted
by the userbase. If no-one downloads a certain patch that would signal the
time has come to remove it.
Paul
--
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-30 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 16:45 [gentoo-dev] GLEP for Deltup package update system John Whitney
2003-07-30 9:43 ` Paul de Vrieze [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-28 22:09 John Whitney
2003-07-29 9:14 ` bdharring
2003-07-29 12:20 ` Kurt Lieber
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=200307301143.43384.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-dev@gentoo.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