apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@covalent.net
Subject Re: cvs access for httpd group
Date Mon, 04 Dec 2000 14:38:16 GMT

> I think we will need to do that.  The problem with ampersand modules
> is that they naturally assume that both modules are owned by the same
> groups.  If we use one within httpd for apr, then we are assuming that
> everyone doing a writable checkout of httpd should also have a writable
> apr.  As much as I believe that is true now, I'd hate to have to manage
> it going forward.  If we used the -R freebsd thing that Brian mentioned,
> then it forces httpd people to have a read-only apr tree even when they
> do have write access to apr.
> So, it seems to me that the best method is the buildconf check,
> allowing the developer to choose where they get their apr.

There is one more advantage to this.  It will allow us to add a flag to
buildconf to specify a different APR.  I know it sounds like that flag
should be in configure, but we actually need APR in buildconf, so it would
need to go there.


Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131

View raw message