Module names

[Dennis Veatch]

On Friday 08 July 2005 11:15 am, Eric Sandall wrote:
> Hi all,
>
> Here's a thought from an outside observer (feel free to ignore/flame
> ;)): Modules should be named in all lower-case. I've been through this
> before on another list and figured I'd share it with you. ;) The
> reason: simplicity. No longer will users/devs have to remember/lookup
> if it's GIT, Git, or git or perhaps Mozilla or mozilla, R or r, etc.
> They will all be git, mozilla, r, etc.
>
> The bad side of this is renaming old modules, which is not fun (I can
> attest to that ;)). So the best (IMO) path to this is to start by
> requiring new modules to be lower-cased and then rename older modules
> as you have time. This would probably be a good way for people new to
> Lunar to help out (it's relatively simple, gets people familiar with
> how modules look and how they can modify them, etc.).
>
> One issue you'll want to take care if is migration. If you just rename
> R to r (e.g.) then users who had R installed will now still have R
> installed, but no module to update/remove R. One way to do this is
> make R a 'blank' module (does nothing), have it depend on r, and have
> r conflict/remove R once it's installed.
>
> Enjoy! :)
>
> -sandalle

I'm not a lunar dev but have observed the module naming scheme we use reflects 
(as closely as possible) the naming scheme used by whom ever developed the 
application as far as the name of the source file goes.

For example R. The source file is R-2.1.1.tar.gz and when extracted is 
R-2.1.1. Putting everything in one case would require some additional 
manipulation of names that maybe does not need be done with the current 
method.