Re: Naming clash

On Wed, 26 Jan 2005, Greg Beaver wrote: > There are several possibilities here. Because of the need for the -n > switch when installing extensions from pecl, I was planning to add a new > command "pecl" (oddly enough :) to handle this. It would mean adding a > little magic into the pear installer (easy to do) so we would see: Or just make it a shell script that calls "pear -n pecl $@" ... > $ pear install sqlite > SQlite is a pecl extension, please use the "pecl" command > $ pecl install sqlite > install ok channel://pecl.php.net/SQLite-1.whatever > > Does this sound reasonable to people? Yes > Note: there are some other interesting side effects. #1, all new > releases would need to use package.xml 2.0. Fortunately, "pear convert" > will automatically convert a package.xml 1.0 to package.xml 2.0, and > then any changes can be done with simple editing. In addition, to > maintain BC with older PEAR versions, packages would need to be packaged > with both a package.xml 1.0 and 2.0, which is also very simple: "pear > package package.xml package2.xml" Not much of a problem either... perhaps "pear package" should figure automatically out if there is a package.xml and a package2.xml. regards, Derick