Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 236532
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 105379
Assigned To: Gentoo Games <games@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Zeev Tarantov <zeev.tarantov@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 236532 depends on: Show dependency tree
Bug 236532 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-09-03 05:04 0000
The Wesnoth developers provide xdelta files to upgrade between the minor
versions of the tarballs. I have successfully used them every time.
I use xdelta-1.1.4 (http://code.google.com/p/xdelta/) to create the .tar file
for the next version from the tar file of the current version. Then I bzip2 the
tar file and the resulting .tar.bz2 file passes the checksumming/hash test
portage performs, so I know it's the same as downloading the whole file.
A minor problem of xdelta-1.1.4 is that I need to feed it the uncompressed
source tar (it can write to pipe for the compression of the target, but can't
read the source from pipe) so the operation takes some disk space. Still faster
than downloading!
I propose to make it possible for the ebuild to see that I have the previous
version's tarball and automatically enable this functionality. Obviously this
would depend on xdelta being installed. If I knew how, I would have written a
patch, but I'm a newb. Can't be that hard though!

Reproducible: Always

Steps to Reproduce:
1. install wesnoth-1.4.4
2. upgrade to wesnoth-1.4.5


Actual Results:  
see it download 150MB.

Expected Results:  
portage notices I have old tarball, downloads 2MB, creates and tests new
tarballs, proceeds to use it regularly.

------- Comment #1 From Gilles Dartiguelongue 2008-09-03 06:46:38 0000 -------
this is probably some sort of portage feature request because I frankly don't
see a simple way to do this at the ebuild level.

Maybe specifying the same base tarball in X ebuilds and then adding relevant
deltas to each new revision, but how many deltas to keep ?

------- Comment #2 From Zeev Tarantov 2008-09-03 13:52:35 0000 -------
I didn't even think about layering the deltas. Yes, if I have wesnoth-1.4.0 I
can patch it to 1.4.5 by applying the deltas in order. I am not sure if it will
save me time, but on dialup it surely will be faster than downloading the full
1.4.5. Also, some people pay for their bandwidth. They host deltas on
sourceforge that can upgrade between major versions. What do you mean by "but
how many deltas to keep"?

I think I know how to make an alternate ebuild for wesnoth-1.4.5 that depends
on the tarball for 1.4.4 and the xdelta. But how can I teach portage about
choosing intelligently between the two options? Is there really no way?

------- Comment #3 From Jeremy Olexa (darkside) 2008-09-03 14:39:24 0000 -------
I see your point but it is up to the maintainer at this point. Unless someone
provides a patch'ed ebuild, etc.

------- Comment #4 From Mr. Bones. 2008-09-03 14:46:43 0000 -------

*** This bug has been marked as a duplicate of bug 105379 ***

------- Comment #5 From Azamat H. Hackimov 2008-09-03 20:08:38 0000 -------
Try to use deltup - it's better solution than xdelta

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug