Dear developers, I committed some changes in the CVS that enable the installation to install the Bulgarian ICD10. Elpidio advised me to commit in the g2_deployment_2_1 as this is supposed to be the branch for the d2.1 release of care2x.
Now, I am supposed to generate a patch release with this new feature, but I see that the g2_deployment_2_1 branch is not in a working state and does not contain the functionality released with "2G Deployment 2.1 FULL PACK + PATCHES D-2.1.0.1". If I install an export from CVS g2_deployment_2_1 branch, the care2x does not work properly. When I try to access /index.php, I receive the following error: Fatal error: session_start(): Failed to initialize storage module: user (path: /tmp) in /usr/local/apache/htdocs/care2x-g2/include/inc_environment_global.php on line 106 This error is not observed if I install an export from CVS elc_tanzania-0-2 branch or if I install the "2G Deployment 2.1 FULL PACK + PATCHES D-2.1.0.1" file release. However, there are visual difference between the latter two. Definitely, the above error is fixed somewhere, but not in the g2_deployment_2_1 branch. Or, maybe, it is introduced there after the file release... I make all installations on one and the same system with the following LAMP installation, which works perfectly with the "2G Deployment 2.1 FULL PACK + PATCHES D-2.1.0.1" file release: Apache 1.3.33 PHP 4.3.11 MySQL 4.0.25 I installed the LAMP following this guide: http://www.lamphowto.com/lamp.htm I also see some strange differences in the install.php file between different branches/releases. In the g2_deployment_2_1 branch the install.php uses the care_db_structure_b200_auto_$dbid.sql script to build the db structure. In elc_tanzania this script care_db_structure_d21_auto_$dbid.sql and in the 2G D2.1 FULL PACK release the script is care_db_structure_b201_auto_$dbid.sql. The last script is not present in the g2_deployment_2_1 branch at all. Another strange thing are the /Care2002/install/sql/icd10_bs/* files. These files are not present in the g2_deployment_2_1 branch, but they are in the elc_tanzania-0-2 and in the 2G D2.1 file release. Maybe they is a lot of more files like the described above. I have the feeling that G2 D2.1 FULL PACK file release is not made from the g2_deployment_2_1, but from some compilation of files taken from several branches. Is it possible to spend some efforts to get the g2_deployment_2_1 branch in a good consistent state? I suppose most of the things that has to be done is to merge changes committed to other branches into the g2_deployment_2_1 branch. I think this is the only way to release further patches of the D2.1 version in a comfortable manner. Thanks and regards Kaloyan ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Care2002-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/care2002-developers
