Re: Re: dependencies and applications
| From: | Stefan Neufeind | Date: | Thu, 21 Aug 2003 13:58:01 +0000 |
| Subject: | Re: Re: dependencies and applications | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-20261@lists.php.net to get a copy of this message | ||
On 21 Aug 2003 at 15:49, Pierre-Alain Joye wrote:
> On Thu, 21 Aug 2003 10:14:24 +0800
> Alan Knowles <alan@akbkhome.com> wrote:
>
> > I think it should follow unix standard here..
> >
> > $phpdir/pear/MDB.1.0.php
> > $phpdir/pear/MDB.2.0.php
> > where
> > $phpdir/pear/MDB.php is softlinked to $phpdir/pear/MDB.2.0.php
> >
> > on windows you will have to copy the latest one into place....as it
> > doesnt have softlinks...
> >
> > one of the beauties about pear at present is the direct mapping of
> > classname=>include path.. - which makes locating code alot
> > simpler...
> >
> > I would also suggest making this as a configuratable option., as
> > it's a bit of an overhead.. for alot of installations.
> >
> >
> > I missed though why you could not just point php_dir at another
> > folder, then call the installer internally to install all the
> > packages in order...
>
> PEAR already supports multiple installations folder using the same
> pear command.
>
> I do not like that much the MDB.1.0.php things or whatever it will be
> named.
>
> If you need the new version, upgrade it in the right install. If you
> like to test major release, install a new tree.
>
> This feature sounds like creating a mess to me :). And I'm not sure
> it'll be possible to make it. How could I include the right file? As
> Alan told us, win32 platform cannot use links, this is another stoping
> point.
Maybe not use MDB/MDB.php any longer after 2.0 or 2.5 as I proposed?
Instead MDB/2.0/MDB.php could be made available on next minor release
of pear as well - so installing all packages twice would be a clean
solution I guess. This doesn't take MUCH more harddisk and is only
needed until 2.5. Maybe if we introduce the warning-thing in 2.0 -
and as of 2.5 we drop BC completely.
Another solution I can think of for the moment would be to have
MDB/MDB.php be automatically generated and simply contain an
include('MDB/2.0/MDB.php');
since this seems similar to a "link" under Linux and works on all
systems.
Requesting more feedback
Stefan