| Summary: | games-strategy/wesnoth: use xdelta provided by upstream to save ~150MB on minor version upgrades | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Zeev Tarantov <zeev.tarantov> |
| Component: | New packages | Assignee: | Gentoo Games <games> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.wesnoth.org/wiki/Download_Xdeltas#Source_code | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Zeev Tarantov
2008-09-03 05:04:44 UTC
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 ? 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? I see your point but it is up to the maintainer at this point. Unless someone provides a patch'ed ebuild, etc. *** This bug has been marked as a duplicate of bug 105379 *** Try to use deltup - it's better solution than xdelta |