Re: PEAR on Windows

From: Date: Mon, 15 Jul 2002 20:12:17 +0000
Subject: Re: PEAR on Windows
References: 1 2 3 4 5 6  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-1889@lists.php.net to get a copy of this message
On Sun, 2002-07-07 at 22:55, Shane Caraveo wrote: > Stig S. Bakken wrote: > > On Thu, 2002-07-04 at 10:19, Martin Jansen wrote: > > > >>On Wed Jul 03, 2002 at 11:3839PM +0200, Jonas Koch Bentzen wrote: > >> > >>>Martin Jansen skrev: > >>> > >>>>On Wed Jul 03, 2002 at 08:3928PM +0200, Jonas Koch Bentzen wrote: > >>>> > >>>> > >>>>>With PHP 4.2.1, does PEAR work out of the box on Windows *without* the > >>>>>user having to add the PEAR directory to his/her include_path as > >>>>>described on > >>>>>http://pear.php.net/manual/en/faq.windows.php ? > >>>>> > >>>>>I'm sorry I can't test this myself - I'm a Linux user. > >>>> > >>>> > >>>>The path is *not* added automatically. (At least that's what > >>>>happened when I installed the binary package on my windows box here.) > >>> > >>>Is there any way we could make it do that? The PHP binary must know > >>>where the base php directory is, and thus where php/pear is, right? > >> > >>I don't know much about the internals of PHP's build system, but I > >>think that adding the PEAR directory to include_path during > >>installation is more a job for the guys on php-dev@lists.php.net. > >>Can you post your proposal there and here what they think? > > > > > > Since this is a Windows issue, it should be done in the Windows > > installer IMHO. It would make my life and go-pear's job a lot easier > > too. :-P > > > > - Stig > > I had only one real issue, in pear.in there is @include_path@ and > @pear_version@. I am assuming that these get replace during install on > linux. Couldn't go-pear do the same for windows, or can we just get rid > of them. -c inidir works from pear.bat, and how important is the > version anyway ;). Actually, these two variables are replaced by the PEAR installer, and this should happen for Windows as well as Unix. If it doesn't, it's a bug. The difference between this and the traditional autoconf replacements is that autoconf does replacements when building, while the PEAR installer does them while installing the package on the destination system. - Stig -- Stig Sæther Bakken, Fast Search & Transfer ASA, Trondheim, Norway http://pear.php.net/wishlist.php/ssb

« previous php.pear.general (#1889) next »