You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Tim Moloney <mo...@mrsl.com> on 2002/04/15 14:36:59 UTC

dependencies - was [Patch] Rename apr_explode_time

Thom May wrote:
> To play nice with the patch I just sent to APR:
> rename apr_explode_time to apr_time_exp_tz

Now that Apache 2.0 is released, will Subversion stabilize the
versions of the software that it depends on?  Or will it continue
to require the latest versions of httpd, apr, neon, etc.?

This is just a question.  I'm not suggesting or insinuating
anything.  =)

-- 
Tim Moloney
ManTech Real-time Systems Laboratory
2015 Cattlemen Road                             \     /
Sarasota, FL  34232                     .________\(O)/________.
(941) 377-6775 x208                        '  '  O(.)O  '  '


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: dependencies - was [Patch] Rename apr_explode_time

Posted by Blair Zajac <bl...@orcaware.com>.
Greg Stein wrote:
> 
> On Mon, Apr 15, 2002 at 11:05:53AM -0500, Karl Fogel wrote:
> > Tim Moloney <mo...@mrsl.com> writes:
> > > Now that Apache 2.0 is released, will Subversion stabilize the
> > > versions of the software that it depends on?  Or will it continue
> > > to require the latest versions of httpd, apr, neon, etc.?
> >...
> > At the moment, of course, this is the case because there isn't much in
> > the development tree that's not also in the release.  I don't know if
> > that will continue to be true in the future; probably Greg Stein would
> > best be able to guess about this.  Greg?
> 
> Actually, we *do* require something past Apache 2.0.35. There was a change
> to mod_dav that inserted another member into the dav_provider structure. We
> were totally compatible with that change (the compiler would automatically
> insert a NULL), but Sander went and explicitly added the NULL :-)
> 
> [ which means, that we now *require* post-2.0.35 ]
> 
> I expect there will be other, similar changes in the mod_dav interface to
> its provider which will cause us to require a newer version of Apache.
> Hopefully, it will be stable, but I'm not going to make guarantees.
> 
> It is also quite reasonable to expect that we're going to want to require a
> later version of Apache to pick up some bug fixes.
> 
> Cheers,
> -g
> 

Also, when you run a Subversion server using SSL with Apache 2.0.35 and
browse the svn repository with Netscape, you'll have runaway httpd processes.
Apache HEAD fixes this issue.  Actually, this isn't a svn issue, just an
Apache issue, but it arose for me out of using svn.

Best,
Blair

-- 
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: dependencies - was [Patch] Rename apr_explode_time

Posted by Greg Stein <gs...@lyra.org>.
On Mon, Apr 15, 2002 at 11:05:53AM -0500, Karl Fogel wrote:
> Tim Moloney <mo...@mrsl.com> writes:
> > Now that Apache 2.0 is released, will Subversion stabilize the
> > versions of the software that it depends on?  Or will it continue
> > to require the latest versions of httpd, apr, neon, etc.?
>...
> At the moment, of course, this is the case because there isn't much in
> the development tree that's not also in the release.  I don't know if
> that will continue to be true in the future; probably Greg Stein would
> best be able to guess about this.  Greg?

Actually, we *do* require something past Apache 2.0.35. There was a change
to mod_dav that inserted another member into the dav_provider structure. We
were totally compatible with that change (the compiler would automatically
insert a NULL), but Sander went and explicitly added the NULL :-)

[ which means, that we now *require* post-2.0.35 ]

I expect there will be other, similar changes in the mod_dav interface to
its provider which will cause us to require a newer version of Apache.
Hopefully, it will be stable, but I'm not going to make guarantees.

It is also quite reasonable to expect that we're going to want to require a
later version of Apache to pick up some bug fixes.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: dependencies - was [Patch] Rename apr_explode_time

Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Tim Moloney <mo...@mrsl.com> writes:
> Now that Apache 2.0 is released, will Subversion stabilize the
> versions of the software that it depends on?  Or will it continue
> to require the latest versions of httpd, apr, neon, etc.?
> 
> This is just a question.  I'm not suggesting or insinuating
> anything.  =)

:-)

I think it will depend on whether we can get everything we need from
the released version of Apache.  If we can, then by definition one
would not need a newer version -- you could call that "stabilization"
I suppose.

At the moment, of course, this is the case because there isn't much in
the development tree that's not also in the release.  I don't know if
that will continue to be true in the future; probably Greg Stein would
best be able to guess about this.  Greg?

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org