According lzo's changelog, it says in 2.01: * Changed the configure system to install the LZO library under the name "liblzo2" so that parallel installation with LZO v1 is possible. This mean we can use gentoo SLOTting to install both 1 and 2 versions, as some programs need patches to compile again lzo 2 as bug #105367 says? Reproducible: Always Steps to Reproduce:
Daniel: Is there a problem with proper include detection or another reason why we can't do this? I just created a slotted ebuild and it installed fine without any conflict. In your gentoo-dev email I missed the information, why the versions can't live safely side by side.
probably can. Just haven't looked into it. I've still got to check all the programs that depend on lzo and see how they behave.
forced slotting of lzo by incrementing the SLOT value by one in the 2.x series ebuilds seemed good enough for me. I package-built both 1 & 2 to tarbz2s then diffed them for clashes and there apears to be no file clashes. And as it is, stuff needing lzo 1 looks in /usr/include for .h's and stuff that wants lzo2 looks in /usr/include/lzo/ so for the time being slotted lzo is a handy trick. untill of course all things depending on lzo are either switched to lzo2 or the ebuild for lzo2 puts symlinks into the /usr/include folder so stuff can find them ( oh yeah, and symlink the lzo2.so 's to the lzo1.so's more likely than not so that things like transcode and mplayer will actually work ;)
done. thankyou
thankyou and closing.
