On Wed, 17 Mar 2010, Bob McConnell wrote:
... snip ...
> IOW, you want to point into the first project's test directory from
> other projects when you can't know the relative paths between those
> projects?
>
> I suspect you will have to manage that on a machine by machine
> basis, unless you can convince the entire development team to create
> a common directory structure that encompasses all projects.
let me emphasize that the layout of the entire "proj" directory will
be consistent across all users and all machines since it will
represent a single SVN checkout, so that's not an issue. of course,
anyone will be free to check it out anywhere they want but once they
do, its structure will be the same across all checkouts.
that's why i think the easiest solution is to define a single
environment variable (say, PROJ_DIR) that anyone can set depending on
where they do the checkout, the PHP code itself will (somehow)
initially consult that variable, and all inclusion from then on will
be based on that. piece of cake, no?
in fact, developers are free to do more than one checkout, work on
them independently, and change PROJ_DIR depending on which one they
want to pick up for their code.
does that more clearly explain what i think the right approach is?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
