On Thu, 19 Jun 2008, Thomas Koch wrote: > I'm about to start implementing > > #010534: Command Line Runner to install/save Database Schemes > > and would like to get your feedback on the following suggestions:
If you're adding new functions, we'd need a requirements document, as well as a design document. > commandline tools in eZComponents > ================================= > > - scripts are executable, without suffix (.php) and start > with ezc-COMPID-, where COMPID specifies the component > they belong to. The COMPID can be a shortcut like > dbschema for DatabaseSchema. If it's a PHP file, it needs to have the .php suffix. > - The ConsoleTools/bin directory contains a script > ezc-base-updatesymlinks, which creates symlinks from the > scripts of all components into the ezc/Base/bin directory > or in another directory. So the user can either put links > in his /usr/bin or in ezc/Base/bin and needs to add only > one directory to his PATH. > > The ezc-base-updatesymlinks script can be reused from > client code to also link their scripts. Therefor the > script accepts a parameter to provide the path to the bin > directories of the client application. Why can't setup-env.sh do this? regards, Derick -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
