hi bill.
If you tell me how, I'll do it.
it's pretty simple
httpd-proxy/modules-2.0/* goes to httpd-2.0/modules/proxy/
./buildconf
It's the other parts I have no clue about.
> -----Original Message-----
> From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]]
> Sent: Fri, May 18, 2001 3:57 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Mod Proxy
>
>
> From: <[EMAIL PROTECTED]>
> Sent: Friday, May 18, 2001 5:46 PM
>
>
> > Things are also a bit different for APR and APR-util. Those are
> > libraries, and an over-riding rule for library developers
> is "don't break
> > backwards compatability". This means that we can continue
> to move APR and
> > APR-util forward, irregardless of the server. If the
> server wants to
> > release, it should go grab the last release of APR and
> APR-util. If the
> > server needs a feature that is in the latest version of APR
> and APR-util,
> > then it either needs to encourage a new release for those
> products, or it
> > needs to wait.
>
> Or to state it simply, httpd builds upon apr(-util), proxy
> builds upon httpd.
>
> Proxy guys or a omnibudsman-RM needs to release the
> httpd+proxy(+other modules?)
> after httpd-2.0 says 'done'.
>
> Or we roll proxy back into the tree. For today, if we can
> add-in proxy to a
> rollup tarball, that's sufficient.
>
> Bill
>
