Re[2]: mmc patch

Tuesday, January 28, 2003, 9:57:23 AM, David wrote:
> On Tuesday, January 28, 2003, at 12:40  AM, Cyb.org wrote:
>> I suggest to create:
>>   -c        - install into current dir
>>   -l        - install into libexec
>>   -p [path] - install into specified path
>> or even rewrite MMC in C. What do you think?
> Funny ... mmc used to be in C ... a long long time ago :) But I made
> the decision that any app whose sole responsibility was to call a bunch 
> of other apps should probably be written in a shell scripting language 
> ... if only for ease of maintenance. I guess a -p option would work ... 
> I'm wondering though if we should just keep -i without the -p option 
> for now and maybe just rewrite it in perl down the road :) I'd hate to 
> make a sub-optimal interface decision here because of limitations in 
> the language mmc is written in.  What do you guys think ?

C code would be more portable if we think about other OS, but anyway
shell will be required if we want to compile something (I mean for
example gcc on Windows cygwin/mingw), so we can stay with sh script.
I think I'll do it like Cory says:

 -i            - install into default libexec
 -I <path>     - install into the specified path
                 (can be absolute or relative)

Agreed? ;)

I suggest also:

 -f            - force to overwrite if module exists in target place
 -F            - don't overwrite if module exists in target place

if none of above is specified script will ask what to do.
If -F will be set and module will exist in target then script will
stop with appropriate comment.

 -V            - show MMC version

Dave - do you know how to make $PROGVERSION variable in MMC right from
CVS version?
 
Cyb.org