Daniel Burrows <[email protected]> writes: [remote apt] > I think a more pragmatic, albeit also uglier, approach is to simply > lock the package database and cache on the remote side, then *copy* all > the apt state structures over the network, copying them back when you're > done (of course, you can use rsync for this instead).
While I have no idea about aptitudes internals, I wonder if it would be possible to, well, merge these two extremes (of doing RPC for everything aptitude does and simply copying all data) - with a bit of magic. If you ensure that you have the same Packages files on both hosts, you can do most of the work locally and just need the remote data to find out what's actually installed, which (I would guess, at least) greatly reduce the amount of data you would need to copy. On the other hand, I am missing some information how things like conffiles changes and debconf prompts should be handled. Amir, have you thought about this problem? Marc -- BOFH #307: emissions from GSM-phones
pgpUVf45U5p53.pgp
Description: PGP signature
_______________________________________________ Soc-coordination mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/soc-coordination
