From: Evan Read <eread@freeshell.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] portage question
Date: Wed, 2 Oct 2002 07:39:08 +0000 [thread overview]
Message-ID: <20021002073908.GA12221@SDF.LONESTAR.ORG> (raw)
In-Reply-To: <20021002092206.0e79a105.bain@reaper.org>
On Wed, Oct 02, 2002 at 09:22:06AM +0200, Henti Smith wrote: > On Tue, 01
Oct 2002 23:09:14 +0000 > Leon Chiver <leon@level7.ro> wrote: > > > I've
installed gentoo and I must say that I'm very pleased whith it. > >
Marvelous job. > > But there's still one feature I'm missing and which
regards the update > > procedure: wouldn't it be nice if we could upgrade
from one version of a > > package to another by only downloading the diff?
A few days before I've > > installed mozilla-1.0, today I emerged 1.0.1.
But I had to download the > > entire 1.0.1 archive, instead of only a diff
file. For people with a > > limited internet access this would be a really
great feature. > > Does anyone know, is such an improvement planned? > > I
had a look on the bugzilla page and did a few searches .. didn't se
anything that pertains to this, but I have to admit .. > In the image of
gentoo this should have been in portage already. > > being able to update
packages just with patches would be really nice for us low bandwidth users
.. >
There was a thread about why the kernel stuff isn't done that way. It was
discussed that it is very hard to allow for people that sit at very
different kernel versions to be able to upgrade with one ebuild. Yes, one
can do all the checks to see what is needed to go from 2.4.x to 2.4.19 (or
even 2.2.x to 2.4.19) and just fetch the right diff, but that is much more
difficult than "get latest source, unpack into /usr/src and patch".
There is nothing stopping anyone from creating thes ebuild themselves and
posting them on the web say "diff2.4.16to2.4.19.ebuild" and giving people
the ability to use them , even if they don't get commited.
Back to Mozilla, mozilla is a less complicated beast. If someone has a
diff, then numberous ebuilds can be created to cover all the bases, or
build the logic into one ebuild. Maybe email the maintainer to ask "why
not" and if he says "because", then write one yourself ;)
--
Evan Read
http://eread.freeshell.org
"The future comes 60 minutes an hour no matter who you are or what you
do."
The Screwtape Letters - C.S. Lewis
next prev parent reply other threads:[~2002-10-02 7:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 23:09 [gentoo-dev] portage question Leon Chiver
2002-10-02 7:22 ` Henti Smith
2002-10-02 7:39 ` Evan Read [this message]
2002-10-02 9:02 ` Alexander Gretencord
2002-10-02 9:12 ` Paul de Vrieze
2002-10-02 12:28 ` Toby Dickenson
2002-10-02 12:34 ` Toby Dickenson
2002-10-02 10:06 ` Henti Smith
2002-10-02 11:53 ` Christian Skarby
2002-10-02 11:54 ` Henti Smith
2002-10-02 12:23 ` Christian Skarby
2002-10-02 12:26 ` Henti Smith
2002-10-02 14:12 ` Alexander Gretencord
2002-10-02 14:11 ` [gentoo-dev] " Leon Chiver
2002-10-03 9:10 ` Paul de Vrieze
-- strict thread matches above, loose matches on Subject: below --
2001-08-25 15:26 [gentoo-dev] Portage question Christopher Burgess
2001-08-25 15:36 ` Mikael Hallendal
2001-08-25 14:57 Christopher Burgess
2001-08-25 15:06 ` Mikael Hallendal
2001-08-25 15:20 ` Daniel Robbins
2001-08-25 15:32 ` Mikael Hallendal
2001-08-27 8:48 ` Djamil ESSAISSI
2001-01-30 21:23 [gentoo-dev] useradd q Dave Bresson
2001-01-30 21:57 ` Achim Gottinger
2001-01-30 23:14 ` [gentoo-dev] portage question John McCaskey
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=20021002073908.GA12221@SDF.LONESTAR.ORG \
--to=eread@freeshell.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