Bug#60810: contents.gz package
On Sat, Jan 15, 2005 at 10:09:07AM -0500, Justin Pryzby wrote: [snip] I think the only sensible and simple thing to do is to provide a zsync file for the Contents files (zsync can 'look into' gz to rsync just the changes). Then every user can use a cron job to zsync the file to his system on a daily, weekly, monthly, whatever basis. zsync uses the http protocol so any http mirror carrying the Contents files will do as source. So maybe an debian-contents-updater package. It contains some cronjob entry, maybe a debconf question, or it uses /etc/defaults/. Yes, that would work nicely, I think. what about including this (zsync'ed Contents plus cronjob) in apt-file (which needs Contents anyway) or including a symlink for apt-file so it uses it instead of downloading a new one on apt-file update filippo -- Filippo Giunchedi GNU/PG key: 6B79D401 Random signature follows: Date: Tuesday, 2002/10/22 - 08:09 dselect proves the existence of Satan. It's the worst part of Debian.
Bug#60810: contents.gz package
Goswin von Brederlow wrote: I think the only sensible and simple thing to do is to provide a zsync file for the Contents files (zsync can 'look into' gz to rsync just the changes). Then every user can use a cron job to zsync the file to his system on a daily, weekly, monthly, whatever basis. zsync uses the http protocol so any http mirror carrying the Contents files will do as source. What about creating a package to do this automatically (using debconf to ask how often to run)? It could be a really small package (just one shell script and docs) and lintian et al could depend/recommend/suggest it. -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GAT/CM$/CS$/CC/IT$/M/S/O/U dpu s+:++ !a C++$C+++$ UB+++$L$*-- P+++$ L+++()$ E-(---) W+++$ N(+) o? K- w--(---) O? M V? PS++@ PE-@ Y+@ PGP++(+++)$ t? 5? X? R tv--(-) b++(+++)@ DI? D? G e- h* r? z* --END GEEK CODE BLOCK-- David Mandelberg [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Bug#60810: contents.gz package
On Sat, Jan 15, 2005 at 07:12:05AM +0100, Goswin von Brederlow wrote: Justin Pryzby [EMAIL PROTECTED] writes: Could we have a package which provides /usr/share/.../Contents.gz? Not sure that share/ is the right place. And as Matt said, versioning is a potential problem. But lintian (and others: apt-file) could depend on this package (say, debian-dist-contents). Justin First of all how do you plan to update the testing package every day? That would be ideal.. They should reflect the testing Contents, right? Contents of whatever is installed, preferably. You also have to release a new version every day. That is an 8MB deb per arch and a source containing all 13 archs. That is 208MB updates per day and suite. ~400MB for testing and unstable every day. Are architectures Contents ever significantly different? Still way way to much data on a daily basis. Hadn't thought of that. I think the only sensible and simple thing to do is to provide a zsync file for the Contents files (zsync can 'look into' gz to rsync just the changes). Then every user can use a cron job to zsync the file to his system on a daily, weekly, monthly, whatever basis. zsync uses the http protocol so any http mirror carrying the Contents files will do as source. So maybe an debian-contents-updater package. It contains some cronjob entry, maybe a debconf question, or it uses /etc/defaults/. Yes, that would work nicely, I think. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#60810: contents.gz package
David Mandelberg [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: I think the only sensible and simple thing to do is to provide a zsync file for the Contents files (zsync can 'look into' gz to rsync just the changes). Then every user can use a cron job to zsync the file to his system on a daily, weekly, monthly, whatever basis. zsync uses the http protocol so any http mirror carrying the Contents files will do as source. What about creating a package to do this automatically (using debconf to ask how often to run)? It could be a really small package (just one shell script and docs) and lintian et al could depend/recommend/suggest it. Obviously. :) MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#60810: contents.gz package
Justin Pryzby [EMAIL PROTECTED] writes: Could we have a package which provides /usr/share/.../Contents.gz? Not sure that share/ is the right place. And as Matt said, versioning is a potential problem. But lintian (and others: apt-file) could depend on this package (say, debian-dist-contents). Justin First of all how do you plan to update the testing package every day? They should reflect the testing Contents, right? You also have to release a new version every day. That is an 8MB deb per arch and a source containing all 13 archs. That is 208MB updates per day and suite. ~400MB for testing and unstable every day. Ok, you can probably use the Contents-i386.gz and diffs for other archs bringing it down to maybe 200MB a day. Then use a different compression and maybe get it to 100Mb. Still way way to much data on a daily basis. I think the only sensible and simple thing to do is to provide a zsync file for the Contents files (zsync can 'look into' gz to rsync just the changes). Then every user can use a cron job to zsync the file to his system on a daily, weekly, monthly, whatever basis. zsync uses the http protocol so any http mirror carrying the Contents files will do as source. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#60810: contents.gz package
Could we have a package which provides /usr/share/.../Contents.gz? Not sure that share/ is the right place. And as Matt said, versioning is a potential problem. But lintian (and others: apt-file) could depend on this package (say, debian-dist-contents). Justin
