Bricolage Apache2 Success

I have successfully got Bricolage to work with Apache2.  I
have not fully
tested it yet and expect to see some residue wonkiness, but
for the most part
it's up and running.  The biggest question I have is how
long should there be
support for Apache 1.3?  The change over affects so many
modules it would be
very straightforward to upgrade everything as of a certain
release and then
look at adding support for Apache 2.2.

How many would be opposed to this option?  We could do a
check in every place
to make it somewhat seamless although IMO it would be more
trouble than it's
worth.

Chris 

Chris Heiland
Web Developer
425.352.3658
Web Services
Information Systems, Campus Box 358540 
University of Washington Bothell

That's great!  How did you get around the segfault issue?

>I have successfully got Bricolage to work with Apache2. 
I have not fully
>tested it yet and expect to see some residue wonkiness,
but for the most part
>it's up and running.  The biggest question I have is how
long should there be
>support for Apache 1.3?  The change over affects so many
modules it would be
>very straightforward to upgrade everything as of a
certain release and then
>look at adding support for Apache 2.2.
>
>How many would be opposed to this option?  We could do a
check in every place
>to make it somewhat seamless although IMO it would be
more trouble than it's
>worth.
>
>Chris
>
>Chris Heiland
>Web Developer
>425.352.3658
>Web Services
>Information Systems, Campus Box 358540
>University of Washington Bothell


-- 
Matt Rolf, J.D.
Web Technology Analyst
Computing Services
Denison University
(740) 587-6537

On Thu, 15 Mar 2007, Chris Heiland wrote:
> I have successfully got Bricolage to work with Apache2.
 I have not fully
> tested it yet and expect to see some residue wonkiness,
but for the most part
> it's up and running.  The biggest question I have is
how long should there be
> support for Apache 1.3?  The change over affects so
many modules it would be
> very straightforward to upgrade everything as of a
certain release and then
> look at adding support for Apache 2.2.
>
> How many would be opposed to this option?  We could do
a check in every place
> to make it somewhat seamless although IMO it would be
more trouble than it's
> worth.

Patch, please? 

On Thu, Mar 15, 2007 at 10:06:32AM -0700, Chris Heiland
wrote:
> I have successfully got Bricolage to work with Apache2.
 I have not fully
> tested it yet and expect to see some residue wonkiness,
but for the most part
> it's up and running.  The biggest question I have is
how long should there be
> support for Apache 1.3?  The change over affects so
many modules it would be
> very straightforward to upgrade everything as of a
certain release and then
> look at adding support for Apache 2.2.
> 
> How many would be opposed to this option?  We could do
a check in every place
> to make it somewhat seamless although IMO it would be
more trouble than it's
> worth.
> 
> Chris 
> 
> Chris Heiland
> Web Developer
> 425.352.3658
> Web Services
> Information Systems, Campus Box 358540 
> University of Washington Bothell
> 
> 
Hopefully, we can get Apache 2.x (0,1,2,...) support working
at the
same time. We are rolling out 2.2 now and Bricolage is the
only app
that will not work. If we need to cease support for Apache
1.3, now
it the time to start deprecating it.

Ken

On Mar 15, 2007, at 10:06, Chris Heiland wrote:

> How many would be opposed to this option?  We could do
a check in  
> every place
> to make it somewhat seamless although IMO it would be
more trouble  
> than it's
> worth.

I'd be loathe to drop 1.3. There shouldn't be *that* many
differences  
between them. Can you send us a patch so we can see what
needs to  
change?

Thanks,

David

Forgot to mention, this patch also needs to be applied:

http://marc.theaimsgroup.com/?l=mason&m=1
15285262409950&w=2

Chris


-----Original Message-----
From: David E. Wheeler [mailto:davidkineticode.com]
Sent: Thu 3/15/2007 12:05 PM
To: devellists.bricolage.cc
Subject: Re: Bricolage Apache2 Success
 
On Mar 15, 2007, at 10:06, Chris Heiland wrote:

> How many would be opposed to this option?  We could do
a check in  
> every place
> to make it somewhat seamless although IMO it would be
more trouble  
> than it's
> worth.

I'd be loathe to drop 1.3. There shouldn't be *that* many
differences  
between them. Can you send us a patch so we can see what
needs to  
change?

Thanks,

David

On Mar 15, 2007, at 12:41, Chris Heiland wrote:

> Forgot to mention, this patch also needs to be
applied:
>
> http://marc.theaimsgroup.com/?l=mason&m=1
15285262409950&w=2

I actually have a better fix than that checked into my svn 

repository. It has been there a while—I forgot about it.
I'll try to  
get a new release out soon.

If you want to try it, it's here:

   https://svn.kineticode.com/Params-CallbackRequest/trunk/


Best,

David

Chris Heiland wrote:
> I have successfully got Bricolage to work with Apache2.
 I have not fully
> tested it yet and expect to see some residue wonkiness,
but for the most part
> it's up and running.  The biggest question I have is
how long should there be
> support for Apache 1.3?  The change over affects so
many modules it would be
> very straightforward to upgrade everything as of a
certain release and then
> look at adding support for Apache 2.2.
> 
> How many would be opposed to this option?  We could do
a check in every place
> to make it somewhat seamless although IMO it would be
more trouble than it's
> worth.
> 
> Chris 

That's great news Chris,

I would love to see 2.x support sooner rather than later. 
Right now
Ubuntu Edgy is at 2.0.55,  Mandriva 2007 and Fedora 6 are
already at
2.2.3.  The Apache foundation has released 2.2.4 and they
"strongly
recommend that users of all earlier versions, including 1.3
family
release, upgrade to to the current 2.2 version as soon as
possible" in
the 1.3.37 release announcement.

- cameron

In my excitement I have done very little cleanup and even
less commenting.  I
plan to keep working on this to get to a better point on
both.  Right now
there are two stages to get it up and running.  The first is
to modify the
installation files to get them to allow Apache 2
installation.  The second is
to update the libraries to get them to play well with
everything.

I should also warn that I am running with Apache2::compat,
for production the
methods will need to be updated to their newer counterparts
and this module
should be removed.  I concentrated mostly on getting things
up and running so
Apache2::Request and Apache2::Cookie should be mostly
working as needed.

The current bugs in the system are the 'Find', 'Active', and
'Alias' sections
fail miserably.  I expect these will be easy enough to
change over. 

I have included the patches.  All of them should be run in
the
/usr/src/bricolage/ folder except the fullpatch which should
be run
post-installation.  I hope to simplify the process soon so
this messy
patching does not need to be done.  In any case, enjoy.

http:
//staff.washington.edu/cheiland/bricolage/


Chris


-----Original Message-----
From: Chris Heiland [mailto:CHeilanduwb.edu]
Sent: Thu 3/15/2007 12:41 PM
To: devellists.bricolage.cc
Subject: RE: Bricolage Apache2 Success
 
Forgot to mention, this patch also needs to be applied:

http://marc.theaimsgroup.com/?l=mason&m=1
15285262409950&w=2

Chris


-----Original Message-----
From: David E. Wheeler [mailto:davidkineticode.com]
Sent: Thu 3/15/2007 12:05 PM
To: devellists.bricolage.cc
Subject: Re: Bricolage Apache2 Success
 
On Mar 15, 2007, at 10:06, Chris Heiland wrote:

> How many would be opposed to this option?  We could do
a check in  
> every place
> to make it somewhat seamless although IMO it would be
more trouble  
> than it's
> worth.

I'd be loathe to drop 1.3. There shouldn't be *that* many
differences  
between them. Can you send us a patch so we can see what
needs to  
change?

Thanks,

David

In my excitement I have done very little cleanup and even
less commenting.  I
plan to keep working on this to get to a better point on
both.  Right now
there are two stages to get it up and running.  The first is
to modify the
installation files to get them to allow Apache 2
installation.  The second is
to update the libraries to get them to play well with
everything.

I should also warn that I am running with Apache2::compat,
for production the
methods will need to be updated to their newer counterparts
and this module
should be removed.  I concentrated mostly on getting things
up and running so
Apache2::Request and Apache2::Cookie should be mostly
working as needed.

The current bugs in the system are the 'Find', 'Active', and
'Alias' sections
fail miserably.  I expect these will be easy enough to
change over.

I have included the patches.  All of them should be run in
the
/usr/src/bricolage/ folder except the fullpatch which should
be run
post-installation.  I hope to simplify the process soon so
this messy
patching does not need to be done.  In any case, enjoy.

http:
//staff.washington.edu/cheiland/bricolage/


Chris



-----Original Message-----
From: Chris Heiland [mailto:CHeilanduwb.edu]
Sent: Thu 3/15/2007 12:41 PM
To: devellists.bricolage.cc
Subject: RE: Bricolage Apache2 Success
 
Forgot to mention, this patch also needs to be applied:

http://marc.theaimsgroup.com/?l=mason&m=1
15285262409950&w=2

Chris


-----Original Message-----
From: David E. Wheeler [mailto:davidkineticode.com]
Sent: Thu 3/15/2007 12:05 PM
To: devellists.bricolage.cc
Subject: Re: Bricolage Apache2 Success
 
On Mar 15, 2007, at 10:06, Chris Heiland wrote:

> How many would be opposed to this option?  We could do
a check in  
> every place
> to make it somewhat seamless although IMO it would be
more trouble  
> than it's
> worth.

I'd be loathe to drop 1.3. There shouldn't be *that* many
differences  
between them. Can you send us a patch so we can see what
needs to  
change?

Thanks,

David