Re: [Apachetoolbox-devel] Re: mod_watch in .58: improved (bin attached)

[Toni M. <su...@oe...>]

Hi,

On Fri, Jul 12, 2002 at 10:15:40AM -0700, Kevin J. Menard, Jr. wrote:
> Well, it needs to check for where apxs is.  I don't know why it needs 
> this for a static library (I was under the impression static modules 
> used EAPI), but oh well.

oh - I don't even know what apxs or EAPI is to begin with, but just
hacked on the existing build script to get the paths and flags for
the Apache Makefile right.

> Personally, I think doing this in shell programmin is a PITA.  It works 

Yes. Shell script portability is a well-known problem.

> great on my platform, but ATB has been riddled with hacks to work on 

 :/

The problem is that requiring people to install Perl should preclude
using Apachetoolbox in quite a few corporate environments. OTOH I'm
not sure that I would mind doing so ;)

> the only programmer on it, and getting good grades took precedent over 
> getting that out.  Every now and then I get ambitious and go back to it. 

Oh - I understand.

>   It's in a rather buggy state, but a somewhat workable one too.  If 
> you'd like to help out, we can start it up again.  It's just adding 
> patches to this existing version is much easier than rewriting the whole 
> thing.

Hmmm... if you could mail me the whole thing? Without sources,
please... then I'll take a look, but no promises.

> I think you'll find that more machines have perl than bash, for 

I think you are overly optimistic, or it may be just your and my
regional views. Whatever... We'll only know it if we try.

> instance.  The issue then becomes versions.  IIRC, I couldn't use all 
> the scope keywords (like "our") because they were Perl 5.6 specific, and 
> I'm sure there are many machines out there running 5.00x still.  The 

Yes.

> other thing I was trying to avoid was making people install modules (and 
> I didn't want to just include them in the script, because that would 
> terribly bloat things, while making the coding easier).  So, all in all, 

Hmmm... requiring to install modules into system locations using CPAN
would be BAD (imho), but installing into a local path should be ok,
especially when most Perl modules are only a few KB in size, compared
to several hundred KB or some megs for the "real thing".


Best,
--Toni++