I like the idea, but each such scripton could define its own subcommands. Example above would result in commands:On 07/03/13 09:38, Jan Safranek wrote:
What about to have filename defining the subcommand? It should simplify things a lot.o we need documentation (on wiki), how to create new subcommands + the part in /usr/libexec/lmi/cmd just registers new subcommands and parses command line, calling functions imported from /usr/lib/python2.7/site-packages/lmi/scripts/
Example:
/usr/libexec/lmi/account/list_user /usr/libexec/lmi/account/create_user /usr/libexec/lmi/account/delete_user /usr/libexec/lmi/storrage/create_vg ... pros: - simplifies the process - one file do one thing - the UNIX way - transparency cons: - a lot of files to maintain Any ideas, objections?
/usr/libexec/lmi/account/account
/usr/libexec/lmi/storrage/vg
/usr/libexec/lmi/storrage/md
/usr/libexec/lmi/software/sw
Mm
RR
_______________________________________________ openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel