Re: cvs: pear /PEAR_PackageFileManager ChangeLog NEWS
| From: | Laurent Laville | Date: | Sat, 14 Oct 2006 09:59:55 +0000 |
| Subject: | Re: cvs: pear /PEAR_PackageFileManager ChangeLog NEWS | ||
| References: | 1 2 | Groups: | php.pear.cvs |
| Request: | Send a blank email to pear-cvs+get-42539@lists.php.net to get a copy of this message | ||
Gregory Beaver a écrit :
Laurent Laville wrote:I don't see why its a huge change . Drop export compatible package xml 1.0 require only to remove the PEAR_PackageFileManager2::exportCompatiblePackageFile1() method. If maintainers still want to produce a package.xml 1.0, there are still PEAR_PackageFileManager 1.5.x, as i've noticed lot of them use again. Few of them have already migrated from 1.5.x to 1.6.xfarell Fri Oct 6 12:20:31 2006 UTCModified files: /pear/PEAR_PackageFileManager ChangeLog NEWS Log:update changelogs related to new feature : import all previous tasks files easily+ - exportCompatiblePackageFile1() method is maked as deprecated,Hi Laurent, I'm afraid this is not OK - dropping package.xml 1.0 export is a huge change to the API and not really necessary.+ because package xml 1.0 will not be supported with stable version 1.6.0
We never talked about this idea.And remember, when i told you about implementing full import on PEAR_PackageFileManager class. Same feature i've done now on import all tasks files from a package xml 2.0 with "clearcontents" set to false. I missed it because all of my computers were busy crashing or
having major hardware problems. I understand deprecating the feature to discourage use of package.xml 1.0, but removing it is out of the question. GregLaurent