On Mon, Aug 08, 2005 at 08:24:20PM +0200, Piotr Roszatycki wrote: > I agree that the solution should be backward compatible and consistent with > current php packages. So this is my last proposition: > > INCLUDE_PATH: <snip> > EXTENSION_DIR: <snip> this sounds good. i'm having trouble getting into alioth right now, but if the problem goes away in the next 24 hours i'll commit it. otherwise someone else should as i'll be disconnected from the next for the next week or two. > Should the web application set the include_path and extension_dir variables or > should rely on default settings? What if some administrator will overwrite > the default settings editing php.ini? The application should override them > again with .htaccess? i think they should rely on the default settings if the default settings will work (but there are cases where it won't). On Mon, Aug 08, 2005 at 03:51:34PM -0300, Jose Carlos do Nascimento wrote: > Sorry :) > I read this doc. > I didnt find how to name php modules or classes that arent pear modules. > ex. adodb,, now is libphp-adodb will we keep this ? i don't know if we settled on a naming scheme for php libraries that aren't pear modules. my impression is that they will be the same as those packaged from pear. this is how perl libraries work, anyway. > Pear project control your modules and its impossilbe has 2 modules with > same name or equal files. > > If I make one package,, ex,, libphp-mail or libphp-net,, these > packages will conflict with pear packages, because pear create > /usr/share/php/Net , have we seen an example of this happening? it's a good point in theory but i don't know that it's ever happened. > Then I think its better put pear packages like one big project and > put all files in one directory,, ex. /usr/share/php/pear. i'm kind of indifferent on this. maybe we can make this one more thing to ask the php maintainers. > Yes, > do you know these mantainers ? how we can talk with them ? apt-cache show php4 | grep Maintainer i've occassionally spoken with adam, though not in any official or productive sense. once we're done i'll be happy to hand it to him and others for review. > >>3 - pear packages installed by "pear(VERSION) install" ex., pear5 > >>install DB > >>/usr/local/share/php/(VERSION)/pear > > <snip> > is this in policy draft ? if it's not, i'll put it in. sean --
Attachment:
signature.asc
Description: Digital signature