On Wed, Jul 16, 2003 at 07:26:55PM +0200, Buchan Milne wrote: > AFAIK, they are not always kept locally, whereas AFAIK for update > sources, the descriptions file is always kept locally (so you can easily > diff the current one against the previous one, and show the user new > package updates). And it most likely has the kind of information the > user wants, rather than the changelogs.
The diff will only show you changes since your last urpmi.update. If you haven't installed the updates when you did that it won't help you. So that method will fail in some cases almost certainly. Other sources people might want to get updates from do not have description files. However, there's no reason why I can't add the parsing of those files as an optional output, maybe make it default with the --update option, which only reads sources tagged as update sources with urpmi. > But if there has been an update, which you aren't interested in, you do. > And at present, hdlist for updates for 9.1 is 3.3MB, and synthesis list > won't have any useful information. True. IMHO the hdlist stuff is flawed. Something more along the lines of what yum does would be nicer, which is fetch the headers of packages it needs and just uses a list file to know what updates there are. The problem with this is it makes supporting removeable media a pain. The solution to that is just make removeable media use hdlists, or cache the files it needs from the removeable media when they are added... -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org "What upsets me is not that you lied to me, but that from now on I can no longer believe you." -- Nietzsche
