-=| Steinar H. Gunderson, Thu, May 20, 2010 at 12:01:16PM +0200 |=- > On Thu, May 20, 2010 at 10:10:04AM +0300, Damyan Ivanov wrote: > > I finally have a working patch. Standalone patch and debdiff attached. > > How is this supposed to work? You remove the Makefile.PL calls, and that's > it? Can you explain why this helps?
Note the place of the calls. They are in the 'perl_install' target, invoked by 'make install'. Building here seems unnecessary in the first place, since the main 'make' call has built (and linked) everything already. AIUI, it was added to fix a problem on windows, but seems to break linking on Debian. Upstream log about the change: http://svn.apache.org/viewvc?view=revision&revision=733406 The perl modules were linked against the build location of libapreq2.so. That's obviously broken, so we now rebuild them during make install to link against the installed location. Maybe it makes sense when using rpaths or installing directly (without destdir=), neigher of which is true for the Debian package building. > > Steinar, I really think this issue is RC. Loading a Perl module > > outside a running apache is quite normal operation. I won't play > > ping-pong with the bug severity, but would very much apprecate if > > you release a package with this patch applied. > > The definition of “important” severity level, according to reportbug: > “A bug which has a major effect on the usability of a package, > without rendering it completely unusable to everyone.” This fits quite nicely > into my assessment of this bug. Hm, this motivated me to find some 'normative' backing of my claim. And I've found one :) Squeeze RC policy:[1] ----------------- The purpose of this document is to be a correct, complete and canonical list of issues that merit a "serious" bug under the clause "a severe violation of Debian policy". ... 5. General ... (f) Libraries ... Shared libraries must normally be linked with all libraries they use symbols from. [1] http://release.debian.org/squeeze/rc_policy.txt I think that 'perl -MApache2::Request' can be classified as 'normal' in the above sense.
signature.asc
Description: Digital signature
