Changeset 10045
- Timestamp:
- 07/01/08 16:49:07 (5 months ago)
- Files:
-
- doc/branches/1.1/cookbook/en/plugins.txt (modified) (1 diff)
- doc/branches/1.2/cookbook/en/plugins.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
doc/branches/1.1/cookbook/en/plugins.txt
r9700 r10045 26 26 Various plugins are depending on other plugins to be installed before they can work. In symfony 1.0, this meant the install instructions contained a list of plugins to install before you could install the plugin of your choice. In symfony 1.1, the installation experience of plugins has been enhanced by the dependency features inherited from using a full PEAR channel implementation. To install a plugin and all it's dependencies, symfony issue the command: 27 27 28 $ ./symfony plugin-install install-deps sfGuardPlugin28 $ ./symfony plugin-install --install_deps sfGuardPlugin 29 29 30 30 No more browsing through various wiki pages to find all the install instructions and get everything working, symfony will now take care of the installation of those plugins for you. doc/branches/1.2/cookbook/en/plugins.txt
r9700 r10045 26 26 Various plugins are depending on other plugins to be installed before they can work. In symfony 1.0, this meant the install instructions contained a list of plugins to install before you could install the plugin of your choice. In symfony 1.1, the installation experience of plugins has been enhanced by the dependency features inherited from using a full PEAR channel implementation. To install a plugin and all it's dependencies, symfony issue the command: 27 27 28 $ ./symfony plugin-install install-deps sfGuardPlugin28 $ ./symfony plugin-install --install_deps sfGuardPlugin 29 29 30 30 No more browsing through various wiki pages to find all the install instructions and get everything working, symfony will now take care of the installation of those plugins for you.