Re: dirname(__FILE__)

Lukas Smith wrote:

From: Markus Wolff [mailto:wolff@21st.de] Sent: Thursday, October 17, 2002 1:46 PM To: smith@dybnet.de Cc: 'Wolfram Kriesing'; 'Alan Knowles'; 'PHP PEAR Developer' Subject: Re: [PEAR-DEV] dirname(__FILE__) Am Thu, 17 Oct 2002 13:43:09 +0200 schrieb "Lukas Smith"

<smith@dybnet.de>:

I just noticed one disadvantage of the dirname(__FILE__) approach: Things will be a bit harder to test in CVS this way. I guess that is the disadvantage of the CVS structure of PEAR.

Why is it harder to test things this way? I don´t quite understand... can you please clarify?

Because the relative paths of installed packages do not match their place within the directory structure within the pear CVS. This mean you can get problems when you include other packages or just the standard PEAR.php using dirname(__FILE__) in your package.

try the following script: setupLns.php.gz you can get it from http://wolfram.kriesing.de/programming/index.php i wrote it to solve exactly this problem, what it does is simply create a directory structure as if the files were installed, but all files inside are simply links to the CVS-dir. i am using it at home successfully ... it has some rough edges but it generally works ... might be your solution -- Wolfram .. translating template engine .... http://sf.net/projects/simpletpl .. authentication system .... http://sf.net/projects/auth