Hello Graham,
It seems we'll have to agree to disagree as we obviously differ on
fundamental interpretation. It's hardly a matter of much concern anyway,
as most packagers will have their own spec file by now.
Before withdrawing from this discussion I'd like to add some comments,
if only for
Luc Pardon wrote:
Yes, that was precisely my point. I know of no other packages -
except the kernel and (your version of) apr - that are installed by
default in this way. For all other packages - to the best of my
knowledge - rpm -U is the default way. It is not for naught that kernel
Luc Pardon wrote:
Both apr and httpd ship with generic spec files included. The apr spec
files are designed so that you can install apr-0.x and apr-1.x side by
side without conflicts,
As far as the included apr spec files are concerned, this is simply
not true.
Last time I looked,
OK, I've been poking at the buildconf script a little bit. The
following patch:
Index: buildconf
===
--- buildconf (revision 351458)
+++ buildconf (working copy)
@@ -53,24 +53,32 @@
#
should_exit=0
-apr_found=0
-apu_found=0
torsdagen den 1 december 2005 21.38 skrev Sander Temme:
Note the cp turds: those files are not installed along with APR, so
buildconf cannot copy them over. How come I or no one else noticed
this ever? Probably because these files are not cleaned up by make
Because you never package it like
On Dec 1, 2005, at 1:03 PM, Oden Eriksson wrote:
torsdagen den 1 december 2005 21.38 skrev Sander Temme:
Note the cp turds: those files are not installed along with APR, so
buildconf cannot copy them over. How come I or no one else noticed
this ever? Probably because these files are not
torsdagen den 1 december 2005 23.56 skrev Sander Temme:
On Dec 1, 2005, at 1:03 PM, Oden Eriksson wrote:
torsdagen den 1 december 2005 21.38 skrev Sander Temme:
Note the cp turds: those files are not installed along with APR, so
buildconf cannot copy them over. How come I or no one else
