On 06/18/2009 10:51 PM, Remi Collet wrote: > Hi, > > /usr/share/php is provided by PHP and included in include_dir defaut value. > > So this seems a good place to store "class" file. > > But I think we need a Guidelines > > 1/ to not allow direct use of /usr/share/php > > => use a sub-folder > > Ex : > - php-oauth use /usr/share/php/oauth => ok > - php-xmpphp use /usr/share/php/xmpphp => ok > > See reviews : > - php-hkit > Review https://bugzilla.redhat.com/show_bug.cgi?id=505358 > approved but use /usr/share/php > > - php-PHPMailer > Review pending https://bugzilla.redhat.com/show_bug.cgi?id=505356 > > - php-captchaphp > Review pending https://bugzilla.redhat.com/show_bug.cgi?id=505354 > > This seems straightforward. Not knowing anything about how php discovers modules, how are the subfolders within /usr/share/php recognized? Would people have to modify the include_dir path or patch code or rename files to make this work? > > 2/ to not allow install for Web application > > A web application must install under /usr/share/<appname> > > php-laconica seems to be a web-app installed under /usr/share/php > Should we just add the prohibition on using /usr/share/php to the existing web application Guidelines? And maybe link from the php Guidelines to the Web Application Guidelines prominently? Also, do any php web applications have general use as a library for others to use? Do php plugins need to be able to include pieces of the web application and that would be best done by using /usr/share/php ? Giving alternatives if php applications need to be fixed to not do this would be good. -Toshio
Attachment:
signature.asc
Description: OpenPGP digital signature
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
