Re: Bug tracker code refactoring

Greetings Josef, Most people on this list have no desire to look at or work on the bug tracker code, so it's a good idea to not ask questions about it here. I'm volunteering to mentor you [if your gsoc application is accepted] so as such please either write me or for global discussions write the php-webmaster@ list. Sorry I wasn't clear about that earlier.

I have one question. I'm writing bug tracker README file. There is config.php with MySQL access parametrs (only), but the code is not using them. So i replaced all parametrs in mysql_connection and mysql_select_db functions used in code. Now I can simply write into README file something like : create mysql tables using bugs.sql, edit config.php file with your mysql access ...

Sounds good so far. Also, the DEVBOX constant and perhaps an email address or three.

But there is one problem. Bug tracker have few files in include folder (config.php also), but in code is used only (for example) require_once "prepend.inc" (prepend.inc is in include diretory too). So there should be include folder in php path (or tracker is not working - can't find those files). Is better to write into the README, that include folder must be in php path or to rewrite require_once parameters (using DIRECTORY_SEPARATOR constant and path to include directory) ?

It's better to not force developers to adjust their master include_path directive. Regards, Philip