Pascal Bleser schrieb: >> What about md5sum-ming the filelist, and use the md5sum as key? If a new >> version of a package is released with the same filelist only the md5sum >> needs >> to be transferred. For big packages the compression might be around 100% ;) > > Already done.
No, that's not what was asked for. Just as an example for repomd: You have a repository with package A-1 and B-1. createrepo writes the filelists of both packages into filelists.xml. Now A gets upgraded to A-1.1. Which is a great thing, because the package manager has to download the whole filelists.xml again, even though package B has not been touched at all. What you describe covers only the fact that the metadata aren't downloaded again if nothing changed. But if even the slightest thing changed, everything is downloaded from scratch, even the parts that have not been changed. Solutions: - Use a smarter protocol that can "fix" this design problem, e.g. rsync instead of http/ftp. - Think about a smarter metadata format. SUSE had one (the old plain-text patchinfos) and threw it away in favour of repomd. - Extend the repomd format to suck less, e.g. by splitting filelists.xml into filelists-dec06.xml, filelists-jan07.xml, filelists-feb07.xml so that at least the unchanged filelists from previous months aren't downloaded over and over again. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
