Bug#303597: ITP: php-rss -- RSS parser for PEAR

2005-04-07 Thread Kees Leune
Package: wnpp Severity: wishlist Owner: Kees Leune <[EMAIL PROTECTED]> Package name: php-rss Version : 0.9.2-2 Upstream Author : Martin Jansen <[EMAIL PROTECTED]> URL : http://pear.php.net/package/XML_RSS License : The PHP License,

Bug#294464: ITP: airt -- application for incident response teams

2005-02-09 Thread Kees Leune
Package: wnpp Severity: wishlist Owner: Kees Leune <[EMAIL PROTECTED]> Package name: airt Version : 20050209.1 (latest version will be uploaded) Upstream Author : Tilburg University, The Netherlands <[EMAIL PROTECTED]> URL : http://www.leune.org/air

Re: PHP application packaging policy/best practice?

2005-01-12 Thread Kees Leune
uld require an override / settings-update for each application. The other suggestion so create a branch under /usr/share/php/appname is also a good one; however that might lead to name conflicts as pointed out earlier. -Kees -- Kees Leune <[EMAIL PROTECTED]>

Re: PHP application packaging policy/best practice?

2005-01-11 Thread Kees Leune
are accessible by the PHP interpreter), .plib files (my own extensions; php files meant to be included; not served by apache), and possibly datafiles which are peristent over sessions. Right now, I am leaning to using /usr/share/appname/php /usr/share/appname/lib /var/lib/appname -Kees -- Ke

PHP application packaging policy/best practice?

2005-01-07 Thread Kees Leune
/share because according to the FHS, /usr/share is meant for "all read-only architecture independent data files". Although PHP files are read-only and architecture indepedent, I consider them as programs. Any thoughts? -Kees -- Kees Leune <[EMAIL PROTECTED]>