Re: Issue with PHP Naming guidelines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le 18/07/2009 18:19, Jason L Tibbitts III a écrit :
>>>>>> "CS" == Christopher Stone <chris.stone@xxxxxxxxx> writes:
> 
> CS> No, I'm arguing that a php module as being defined as something
> CS> which puts a .so file under %{_libdir}/php.
> 
> So pear packages aren't PHP modules?  They're all noarch (pretty much
> by definition) and so don't have .so files.

I think tibbs is right in his first post

PHP Web app, (generally under /usr/share/appname) is out of php-*
namespace and is called appname (phpMyAdmin, glpi, foo)

A PHP extension, written in PHP, providing some classes, is installed
under /usr/share/php (to benefit of default include_path) and is under
the php-* namespace, so must be called php-foo (according to the actual
PHP Guidelines)

If I well understand, the question is
Should we make an exception if name already start by php to avoid
php-phpxxx.

Personaly, I think php- prefix should be add to "all" extensions.


+

--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux