Description: ------------ With new stable version 1.0.0 of PEAR_PackageFileManager2, I wanted to try it ASAP, and I was disapointed today at my Office when I see the result. First I thought it was a wrong install , and I did it again here on my house. I've upgraded from PEAR 1.7.2 to PEAR 1.8.1 I've uninstalled old PFM 1.6.3 I've installed PFM plugins 1.0.0, then PFM2 1.0.0 I've try to use my script (package.php) to generate PHP_CompatInfo in PEAR repository without success. I got error below. So I try to change 'filelistgenerator' option from 'cvs' to 'file', and all run fine. My CVS local copy is not broken, and the CVS/Entries still exists. Test script: --------------- See http://cvs.php.net/viewvc.cgi/pear/PHP_CompatInfo/package.php Expected result: ---------------- a new version of package xml 2.0 with good results Actual result: -------------- PEAR_PackageFileManager_Plugins Error: Directory "C:/php/pear/PHP_CompatInfo" is not a CVS directory (it must have the CVS/Entries file)

I just tried to checkout the code and do php package.php make of the bat and it worked - Except I had to fix $packagefile since you used a full windows path (you might want to point it to package2.xml so other people can use CVS) I also tried to add a new file called helgi.php in the base dir of PHP_CompatInfo, regenerate with filegenerator set to cvs, then it didn't add helgi.php but when I put file then it got added, so I am not able to reproduce this problem. Please make a new checkout of PHP_CompatInfo and see if this still happens. Keep in mind it might be a problem only on Windows, if you do the fresh checkout then we can exclude couple of problems.

*prod* Laurent, any luck? (... can I close it?)

Daniel, It's up to Helgi to choose what to do. I've already gave a solution in the PEAR dev mailing list 13 days ago. Have a look on my answer: [1] - http://news.php.net/php.pear.dev/51817 And Helgi : [2] - http://news.php.net/php.pear.dev/51818

Any chance of applying the fix of Laurent's?

I confirm that the proposed patch [1] works. The same bug affects the SVN plugin, BTW, and bug #16287 is probably a duplicate of this one. [1] http://news.php.net/php.pear.dev/51817

The change that Laurent would like to have removed would undo a fix for symlinked files on unix (bug #15244).

The problem seems only to appear on Windows. Since Windows symlinks are not really widely used, it's safe for now that we add a windows specific check.

Please test the changes in svn which should fix the issue on windows and report back here.

Christian, The latest patch available on SVN is perfect. No problem detected on Windows platform.

Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at http://pear.php.net/get/ Fixed in version 1.0.1 of PEAR_PackageFileManager_Plugins.