> > now that sarge is released with one of the most well tested versions of > > lessdisks, please consider updating lessdisks to the current released > > version, 0.6.2d, or the current cvs (0.7 branch pre-release: Tue Jun 7 > > 22:32:49 UTC 2005), which is very close to a release. > > I'd really like a way to handle upgrades. Or at least know when an > upgrade is possible and when not.
i've been considering this issue over the past several days- it's very important. i'm starting to realise that upgrades from the 0.5 branch to 0.6 and greater are really difficult to do right, largely because a lot of configuration information was moved from the server-side configuration file to the terminal-side configuration file. but maybe it's not as bad as i think. i think 0.6 was smart in moving more into the terminal, as upgrades from 0.6 to future versions will be much easier to handle correctly, and makes the server-side and chroot-side versions of packages less inter-dependent on similar versions (my eventual goal will be to have no inter-dependencies on particular versions, and i think current cvs is much closer to that goal). the main issues i see with upgrades beyond the leap from 0.5 to 0.6 are that a number of configuration file and debconf values have been re-named (and worse, some have changed purpose). renamed configuration/debconf values should be easy enough to detect and update to the new value. the other issues are more difficult to handle, and *concrete* ideas on how *exactly* to handle it would be useful, and of course, code handling it would be ideal. live well, vagrant p.s. should i drop your email in my replies, as the bts should be sending you this mail anyways?
signature.asc
Description: Digital signature
