[EMAIL PROTECTED] on 03/08/2000 03:18:04 PM
>> >Even still, what's wrong with an 'all-in-one' to add something to the module
>> >file as well? (or are you of the 'if it can be in a script, it mustn't be in
>> >the regular program' camp?)
>>
>> I know I'm in the 'if it can be in a script, it mustn't be in the regular
>> program' camp on this one. The reason is that CVSROOT/modules can specify
>> modules in any number of ways. Who's to say what the "right" way is for
*all*
>> sites?
>>
>> Noel
>
>Well, just as a thought, how about taking the line to go into modules
>as an argument?
Too complicated. How do you handle standards like, "Keep the modules file
alphabetized."?
>Or, how about an NFS like approach -- a simple option/options to solve
>90% of the cases, and the other 10% edit the modules file.
Noone knows what 90% of the cases is specially since most people who use CVS
aren't even on this list (this is, of course, a guess on my part). Anyway, it's
impossible to get any statistics if you can't measure the population.
>(Taking module name, and optionally the directory if the module name
>isn't the directory, is probably the 90% level.
You don't know that. Many people use module aliases and the other flags
available in the modules file.
Noel
