Le Mer 12 Janvier 2005 01:31, Matthew Palmer a écrit :
[No Cc needed, as per list policy]
On Tue, Jan 11, 2005 at 11:47:42PM +0100, Pierre Habouzit wrote:
it's _quite_ true that you don't need to play with include_path.
your library has to know it's installed
into
Le Mer 12 Janvier 2005 01:31, Matthew Palmer a écrit :
So you patch libfile2.php to require_once 'mylib/libfile1.php'
instead of just 'libfile1.php'.
oh and btw, the suggestion I did is better (IMHO) :
replace require_once 'libfile.php'; with
require dirname(__FILE__).'/'.'libfile1.php';
On Wed, Jan 12, 2005 at 10:13:05AM +0100, Pierre Habouzit wrote:
Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit :
[No Cc needed, as per list policy]
On Tue, Jan 11, 2005 at 11:47:42PM +0100, Pierre Habouzit wrote:
it's _quite_ true that you don't need to play with include_path.
[No Cc please, as per list policy]
On Wed, Jan 12, 2005 at 10:16:43AM +0100, Pierre Habouzit wrote:
Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit :
So you patch libfile2.php to require_once 'mylib/libfile1.php'
instead of just 'libfile1.php'.
oh and btw, the suggestion I did is
On Wed, Jan 12, 2005 at 10:16:43AM +0100, Pierre Habouzit wrote:
Le Mer 12 Janvier 2005 01:31, Matthew Palmer a ?crit :
So you patch libfile2.php to require_once 'mylib/libfile1.php'
instead of just 'libfile1.php'.
oh and btw, the suggestion I did is better (IMHO) :
replace
Le vendredi 07 janvier 2005 à 14:19 +0100, Kees Leune a écrit :
Hi,
I am preparing an ITP for a PHP application that is currently under
development at my place of employment. While thinking about packaging
it, I was wondering if there is any PHP application policy or best
practice. I am now
hi there,
On Sat, Jan 08, 2005 at 03:05:15PM +0100, Jérôme Warnier wrote:
Any thoughts?
I collected some interesting Debian packaging Web Applications policy
drafts some time ago:
http://glasnost.beeznest.org/articles/184
to throw another link out:
http://people.debian.org/~seanius/policy/
Le samedi 08 janvier 2005 à 18:32 -0500, sean finney a écrit :
hi there,
On Sat, Jan 08, 2005 at 03:05:15PM +0100, Jérôme Warnier wrote:
Any thoughts?
I collected some interesting Debian packaging Web Applications policy
drafts some time ago:
http://glasnost.beeznest.org/articles/184
Quoting Kees Leune [EMAIL PROTECTED]:
Hi,
I am preparing an ITP for a PHP application that is currently under
development at my place of employment. While thinking about packaging
it, I was wondering if there is any PHP application policy or best
practice. I am now leaning to a setup as
On Fri, 07 Jan 2005, Kees Leune wrote:
/usr/lib/appname/php Publicly loadable PHP pages
/usr/lib/appname/libIncluded PHP libraries (not reachable via httpd)
/var/lib/appname Persistant data
/etc/appname/appname.cfg Configuration
/etc/appname/apache.conf Apache
10 matches
Mail list logo
