[Bug 622429] New: package libapr1-devel houses link to libapr1.so instead of package libapr1
http://bugzilla.novell.com/show_bug.cgi?id=622429 http://bugzilla.novell.com/show_bug.cgi?id=622429#c0 Summary: package libapr1-devel houses link to libapr1.so instead of package libapr1 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache@forge.provo.novell.com ReportedBy: alext@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- The softlink /usr/lib64/libapr-1.so -> /usr/lib64/libapr-1.so.0.3.8 is incorrectly placed into the libapr1-devel package instead of the libapr1 package, forcing installation of the devel package to get the correct link for runtime. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=622429
http://bugzilla.novell.com/show_bug.cgi?id=622429#c1
Marcus Meissner
http://bugzilla.novell.com/show_bug.cgi?id=622429
http://bugzilla.novell.com/show_bug.cgi?id=622429#c2
Alex Tsariounov
http://bugzilla.novell.com/show_bug.cgi?id=622429
http://bugzilla.novell.com/show_bug.cgi?id=622429#c3
Marcus Meissner
http://bugzilla.novell.com/show_bug.cgi?id=622429
http://bugzilla.novell.com/show_bug.cgi?id=622429#c4
Michal Vyskocil
tomcat6 should probably requires libapr-devel instead of moving.
Tomcat does not Require libapr1. It should recommend it ...
(or the bug that it looks for .so links should be fixed, and the .so.majorversion should be used)
No, that cannot be done. Java call System.loadLibrary($NAME) is translated into $LIBDIR/lib$NAME.so. And because libapr is loaded by tomcat in runtime by System.loadLibrary($NAME), which is the equivalent of dlopen it is more a plugin than shared library from tomcat's POW. We have few solutions: 1.) Add the libapr-1.so to libapr1 package - not useful for nontomcat/no java users 2.) Let tomcat6 Require/Recommend/Suggets libapr-devel - not useful for tomcat users without apache 3.) Add Supplements: packageand(apache:tomcat6) into libapr-devel
From my POW the best opinion here number 3, because libapr-devel will be installed on system with tomcat6 and apache, which seems like most reasonable situation.
* For the forward compatibility (tomcat7 is in beta phase) I'll change our tomcat packages to provide generic tomcat symbol, so this will work in a future too. Roman: you're the bugowner of Apache project - what's your opinion? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com