Re[6]: mmc patch

$ mmc
 - print full help

$ mmc -n borg
you have to specify also: -d, -f, -i or -I [path]
try 'mmc -h' for help

$ mmc -n borg -i file.moto
 - compile module borg and install into libexec dir
 - if module exists it'll not be replaced and tell user to try -f

$ mmc -n borg -I /home/borg/modules/ file.moto
 - compile module borg and install into /home/borg/modules/
 - if module exists it'll not be replaced and tell user to try -f

$ mmc -n borg -i -I /home/borg/modules/ file.moto
 - compile module borg and install into libexec dir AND /home/borg/modules/
 - if any module exists it'll not be replaced in there and tell user to try -f

$ mmc -n borg -d
 - compile module borg and leave it in /tmp/<mod name>

$ mmc -n borg -f -i -I /home/borg/modules/ file.moto
 - compile module borg and install into libexec dir AND
   /home/borg/modules/ AND overwrites modules with the same name in both
   directories


I have abadon interactivity. If compiled file exists it'll not be
overwrited unless -f is present.
I don't think multiple -i -I <path> are a problem. We could give only
-I <path>, we could only write on www how to hand-compile module, but
that's not the point of creating MMC. I think it should be for users -
not especially for beginners ("what is an apache?.."), but I prefer to
wrote only one short command line instead of two. ;)

# mmc -n borg -f -i -I /home/borg/modules/ file.moto

instead of

# mmc -n borg -i file.moto
# cp -f /usr/local/apache/libexec/mod_borg.so /home/borg/modules/

We could "help" potential user by adding -I flag. :) It could help
also in multi-sever administration as Cory says. :)

Install into './' don't have to be enabled (-l flag?) in MMC when we
have -I.


What you think?

Cyb.org