On Thu, 2004-04-29 at 14:14, Martin List-Petersen wrote: > And to bring that naming issue up again. Wouldn't it be best just to call them > libpear-something og libphp-something ? > > That is the naming scheme mostly used all over Debian (libapache, libperl, etc.) > > I think something like that probably should be defined, before they are introduced. Also versioning (PHP4/5) should be considered in the package namings. Some new PEAR package will only work with PHP5, some work with both. I am not sure how Perl solves this versioning problem, if it exists there :) I also want to note that the PEAR package in Debian should work as the CPAN one. Installation of PEAR packages via "pear install $package_name" should be done in /usr/local... but debian pear packages put them into /usr.. the php.ini just needs to know both paths in the "include_path" option -- Mirco 'meebey' Bauer PGP-Key: http://search.keyserver.net:11371/pks/lookup?op=get&search=0x5051C9B9 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d s-: a--- C++ UL++>++++ P L++$>+++$ E W+++$ N o? K- w++>! O- M- V? PS PE+ Y- PGP>++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r>++ y? ------END GEEK CODE BLOCK------
Attachment:
signature.asc
Description: This is a digitally signed message part