Re: apxs and LIBEXECDIR ?

2004-02-19 Thread Fabio Massimo Di Nitto

Hi David,
sorry for the late reply but i didn't notice this mail until now.

On Tue, 3 Feb 2004, David N. Welton wrote:


 Another thought that crossed my mind.  apxs -q LIBEXECDIR is where
 automated installers might want to put modules, right?

Yes.

 At least if they are using apxs as a guide.

That's correct.

 Another reason why just dying because of modules in that directory is a
 bad idea, IMO...

sorry but i don't understand.. related to what?

If you are talking about #226833 it is pending right now.

Fabio

-- 
user fajita: step one
fajita Whatever the problem, step one is always to look in the error log.
user fajita: step two
fajita When in danger or in doubt, step two is to scream and shout.




Re: apxs and LIBEXECDIR ?

2004-02-19 Thread David N. Welton
Fabio Massimo Di Nitto [EMAIL PROTECTED] writes:

 Hi David,
   sorry for the late reply but i didn't notice this mail until now.

No problem.

  Another thought that crossed my mind.  apxs -q LIBEXECDIR is where
  automated installers might want to put modules, right?

 Yes.

  At least if they are using apxs as a guide.

 That's correct.

  Another reason why just dying because of modules in that directory
  is a bad idea, IMO...

 sorry but i don't understand.. related to what?

 If you are talking about #226833 it is pending right now.

Basically, yes.  If I install a 3rd party module that uses apxs, it
will install in /usr/lib/apache/1.3, and presumably everything will be
working ok untill I try and upgrade and *bang*, my previously
functional installation is broken.

I'm not sure what the 'solution' to this bug is, but if you consider
the number of bug reports that have arrived to date and do some
extrapolation to the number of stable users who will hit this on
upgrade, to me it seems evident that another solution is necessary.  I
wish I were able to suggest something that would make everyone happy,
but I don't have all the world's answers, only some of them;-)

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
 Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/




Re: apxs and LIBEXECDIR ?

2004-02-19 Thread David N. Welton
Fabio Massimo Di Nitto [EMAIL PROTECTED] writes:

 As I said the bug is pending. A fix has been already introduced to
 avoid apache to stop upgrading. Another fix instead is on the way to
 generate .info files from apxs (#228077) but it is still under
 testing and it will not make it for this release

Oh, great!  Well that makes me happy then:-)  Thanks!

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
 Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/




apxs and LIBEXECDIR ?

2004-02-03 Thread David N. Welton

Another thought that crossed my mind.  apxs -q LIBEXECDIR is where
automated installers might want to put modules, right? At least if
they are using apxs as a guide.  Another reason why just dying because
of modules in that directory is a bad idea, IMO...

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
 Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/