> >>>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 was perhaps a little over-ambitious about the time-frame of the 0.7.x branch... :) > >>I'd really like a way to handle upgrades. Or at least know when an > >>upgrade is possible and when not. in CVS, i have included a TODO.upgrades file which documents a number of the changes between versions. near the bottom is notes from an actual 0.5.x to 0.6.x upgrade, and what we needed to change. i have also included some code in the .config and .postinst scripts in distrib/debian to grab info from the older configuration files if appropriate. > > 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. it isn't as bad as i was thinking, since the values are available in /etc/lessdisks/server.config > > 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). > > Sounds good (and sounds like it is worth the wait not releasing 0.6 for > Debian at all). that might end up being quite a wait, from the looks of things. i'm starting to think about backporting some code from the 0.7.x branch and making a newer 0.6.x release with some feature enhancements (but still compatible with other 0.6.x versions)- so it might be worth considering getting 0.6.2d into debian (with kernel-image-netbootable and initrd-netboot-tools disabled). might be putting off 0.7.x even longer, with the goal of breaking it into many smaller parts. hopefully this can be managed without driving me insane. the initrd-netboot split was pretty clear and simple to do- it was already pretty isolated code, but the rest is a little more integrated. we'll see... live well, vagrant
signature.asc
Description: Digital signature
