Bug#372712: apt: pdiff - does not work for long upgrade periods (need thresholds)
Package: apt
Version: 0.6.44.2
Followup-For: Bug #372712
As the other reporter already expressed:
- The .pdiff concept is very good for regular updates
- *BUT* the .pdiff performs poorly if update periods
are not frequent
And example
- After 4 months, kick in "apt-get update"
- It takes hours for .pdiff to complete on modem line
SUGGESTION
Add more intelligence to apt so that it selects the
correct methods based on various factors:
- if (a) enough days have passed or/and
- (b) enough packages have changed
On those conditions, the threshold settings (preferrable
user configurable), would use normal *.deb download method.
The *.pdiff would be used only when the timeframe of previous
update is near enough.
Or, apt could also calculate the count/size of *.pdiff's needed
to get the update done and determine if that would be "too much"
and revert to regular *.deb download.
-- Package-specific info:
-- (no /etc/apt/preferences present) --
-- (/etc/apt/sources.list present, but not submitted) --
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Versions of packages apt depends on:
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-8 GCC support library
ii libstdc++6 4.1.1-8 The GNU Standard C++ Library v3
Versions of packages apt recommends:
pn debian-archive-keyring <none> (no description available)
-- no debconf information
Reply to: