From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage 1.8.1 released
Date: Sun, 30 Dec 2001 10:55:01 +0200 [thread overview]
Message-ID: <0GP500L0BG1EKS@mxout2.netvision.net.il> (raw)
In-Reply-To: <1009698724.11092.2.camel@fluffy>
On Sunday 30 December 2001 09:52, you wrote:
> This depends on how the person that upgraded the package did it.
>
> With this functionality all developers should try to use patches rather
> than the full file (if they are available). I come to think of the
> kernel-sources which always provides patches for updating.
Yes, but on the other hand, after a couple of months like this, the patches
will become too large. That is, all kernel patches from 2.4.0 to 2.4.17 are
probably a lot bigger than 2.4.17 on its own.
The problem is, someone who updates his kernel (in this example) every two
weeks will always want to download patches, and will gain by them. But
someone who installs gentoo for the first time, or hasn't kept his distfiles
dir, will have to download an old package and lots of diffs and will lose by
it.
So we need portage support smart enough to choose between downloading
patches/diffs (if you already have an old version) or the latest version (if
you don't).
> For really large packages it might be nice if we did diff's and uploaded
> to ibiblio.
I'm probably dreaming here, but maybe we coud have some diff auto-generating
system, which could provide a diff between any two versions, like cvs does.
But that's far in the future, if it happens at all.
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next prev parent reply other threads:[~2001-12-30 9:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-30 6:56 [gentoo-dev] Portage 1.8.1 released Daniel Robbins
2001-12-30 7:46 ` slik
2001-12-30 7:52 ` MIkael Hallendal
2001-12-30 8:55 ` Dan Armak [this message]
2001-12-30 16:28 ` Daniel Robbins
2001-12-30 9:20 ` Dan Armak
2001-12-30 16:29 ` Daniel Robbins
2001-12-30 12:04 ` Sebastian Werner
2001-12-30 20:57 ` Sebastian Werner
2001-12-30 21:51 ` jano
2001-12-30 21:42 ` Daniel Robbins
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=0GP500L0BG1EKS@mxout2.netvision.net.il \
--to=danarmak@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