First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 110878
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Default Assignee for Orphaned Packages <maintainer-needed@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Francisco José Cañizares Santofimia <telefrancisco@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 110878 depends on: Show dependency tree
Bug 110878 blocks: 112367
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-10-30 04:14 0000 
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:

------- Comment #1 From Carsten Lohrke 2005-11-01 12:56:42 0000 ------- 
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.

------- Comment #2 From Daniel Black 2005-11-04 21:50:48 0000 ------- 
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.

------- Comment #3 From Kent Fredric 2005-11-12 02:55:57 0000 ------- 
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 ;)

------- Comment #4 From Daniel Black 2005-11-13 01:34:50 0000 ------- 
done. thankyou

------- Comment #5 From Daniel Black 2005-11-13 01:43:16 0000 ------- 
thankyou and closing.
First Last Prev Next    No search results available      Search page      Enter new bug