PEAR trees

> > One of the things that Pear needs is something like a database of > > installed packages. With it, it should be easy to do such things. There > Nice idea, but the problem is to make it 'ISP-safe'. I mean, i should be work > virtual host specific. > I see that you are discussing about dir structure, naming conventions etc.. One solution in between could be that proposed here recently: a coded structure. I dunno why but I liked that idea. > how do you keep backward-compability? > well, an easy way would be something like > include $PEAR_ROOT . "/base.php"; > $base = new base(); > $base->include("package_name"); > > (forgive me if the code wouldn't work (i haven't touched classes yet > (forgive me god)), but you understand what it SHOULD do) > > and then it doesn't matter where you have the package. > AND if you move it and rename it in some way, you just make an alias in the > base.php-file (or base.xml, what do i know?). > > > and this would also help people distribute packages for use in PEAR. > - Gianca