Re: [SMARTY-DEV] path/to/smarty in include_path, package.xml

From: Date: Mon, 29 Sep 2003 09:22:09 +0000
Subject: Re: [SMARTY-DEV] path/to/smarty in include_path, package.xml
References: 1  Groups: php.smarty.dev 
Request: Send a blank email to php-smarty-dev+get-1880@lists.php.net to get a copy of this message
On Fri, Sep 26, 2003 at 07:06:30PM +0200, Roman Neuhauser wrote: > Hi there, > > I've searched the archives @ marc.theaimsgroup.com for package.xml, > which returns 0 hits, and searches for include_path return too many hits > to be any useful, so I'm here. hmm. http://marc.theaimsgroup.com/?l=smarty-general&w=2&r=1&s=package.xml&q=b brought me to http://marc.theaimsgroup.com/?l=smarty-general&m=104641507314947&w=2 > I've always wondered why Smarty assumes to be in the include_path. Not > that it wouldn't work flawlessly when it's in a subdir of a directory > in include_path, but the manual contains e. g. > > // Edit your php.ini file, add the Smarty library > // directory to the include_path and restart web server. > // Then the following should work: > require('Smarty.class.php'); > $smarty = new Smarty; > > The text itself admits in a subtle way that the procedure being > recommended is lame. > > // Install the Smarty library in a subdir of directory that's in > // the include_path. Then the following should work: > require('Smarty/Smarty.class.php'); > $smarty = new Smarty; > > Users do tend to follow bad advice given them in a manual. :) it seems the INSTALL-file from the distribution is not in sync with the SGML-version (which is the source of http://smarty.php.net/manual/en/installing.smarty.basic.php ) . this can be fixed easily. > We've been using 2.1.0 here until a couple of days ago, including Smarty > exactly as above without any problems, I recently upgraded one > development machine to 2.5.0, with the contents of lib/ in > /usr/local/lib/php/Smarty, and the rest in the default locations > (/usr/local/share/examples/smarty etc.), and it just works. > > And here we get to the package.xml file: if Smarty had an official > package.xml file, it could be installed and upgraded with pear(1), > which would be a good thing in itself, but would also fix a real problem > this would create otherwise: Smarty works on Windows, and presence of > make(1) on a win32 box cannot be possibly assumed. pear(1) does run on > windows, so this is IMO a non-issue. > > What do you think? BTW, Alan Knowles posted a package.xml file for > Smarty 2.4.2 to smaty-general@ in February. I don't see any followup to > his message, isn't this an interesting thing? hmm, i can not recall this postings but i'm sure i read smarty-general in february :). if somebody want's to polish the file up a bit to fit to Smarty-2.5.0 or Smarty-2.6.0-RC1 we could add it to the misc-directory of the distribution. then everbody can build his own package like with a rpm-spec-file, right? sorry, i'm not very familiar with pear's package-management system: do you mean by "official" that the package.xml would be on pear.php.net and smarty could be installed/upgraded with "pear install Smarty" or the like without haveing to download it ? or does "official" simply mean the guys on top of Smarty's README-file have to support it and can be blamed if it doesn't work? :-) greetings messju

« previous php.smarty.dev (#1880) next »