Jeff Licquia writes... > Further experimentation seems to indicate that this may be an artifact > of my dynamic linker hack, which is based on glibc 2.3.5, and not on the > actual metadata in the RPM. > > Sorry for the misdiagnosis.
Well I think something good came out of this firedrill and that is I think it may be wrong for alien to be adding library dependencies when converting LSB rpms. Adding those dependencies might be correct for the system that alien is being run on, but could be wrong for a different version of that system (example: converted on etch, broken on sarge) or a different system (example: converted on ubuntu, broken on debian). I also think it's more than just versioned depends, but the dependencies themself, since the package namespaces aren't necessarily the same. So, is it reasonable to expect that someone would convert an lsb rpm on one system and install it on another? If we don't want to allow this then perhaps we need require -i, an maybe even make an "lsb-install" wrapper that runs alien -ci or something. Comments? -- Matt Taggart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
