Re: @foo@ / templates / sub packages

Joe Stump wrote: > 1.) Does anyone have a definitive list of variable names the PEAR > installer will replace via the @foo@ stuff? for the pear-config replacement type: pear config-show every configuration variable can be used For php-const replacement type: any PHP constant or PEAR installer constant For package-info replacement type: any top-level package.xml 1.0 tag like "version" or "name". package.xml 2.0 top-level tags are also supported, and some 2nd level like "api-version" for <version><api>. This is not documented explicitly, but needs to be. All package-info tags are replaced at packaging time. > 2.) Where do people put template files? If you use @data_dir@ and expect > your code to have that expanded how do you easily test without packaging > and installing? check out phpDocumentor - this package is intended to be run from checkout and from pear installation and uses smarty templates. The templates are compiled prior to release, so no changes are made to them. If your templates need modification, then this model isn't good. > 3.) Anyone know where sub packages are documented? what aspect of subpackages? Greg