On Fri, Aug 18, 2000 at 05:05:46AM -0500, Peter Samuelson wrote: > Untested. (Come to think of it, instead of LD_PRELOAD you should use > rpath, which is considered harmful but I think is justified here.)
> Yes, package size doubles, but you must not be worried about size since > you currently statically link against liblvm. The main issue here is > that it's not currently possible to dual-boot 2.2 and 2.4 kernels with > lvm, so migration may be difficult for many people. There is a backport of the 2.4 version of LVM to 2.2, which I have successfully run on a production system for a while now at work, so hopefully yhis system won't be necessary... however, this does still leave a big problem: how to handle the upgrade from 0.8i to 0.8final. If you are currently using LVM 0.8i, then upgrade to 0.8final, LVM will stop working unless you also recompile your kernel. I thought I could maybe make an "lvm-0.8i_0.8i-..." package or something similar, which Replaces: lvm (< 0.8final), and is Recommended by the new lvm 0.8final. So... what I need to know is this: What exactly is the behaviour of apt when upgrading a package. How can I make it so that if you upgrade from the LVM 0.8i pkg to the 0.8final pkg, you get a compatibility package installed by apt or dselect or dpkg, but if you install the package fresh, that doesn't happen. Or should I put some sort of warning in the preinst? The ideal situation would be to have 0.8final the "standard" version for both 2.2 and 2.4 kernels, with a 0.8i compatibility package, IMHO. -- Tom Lees <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
