Module names

[Terry Chan]

Renaming modules to all lowercase is NOT going to happen.  So feel IGNORED.

Especially in the case of GIT and git.  I purposely renamed the ancient
git module GIT for Gnu Interactive Tool, so that Linus Torvalds new "git"
would become the moonbase "git" module.  It was either that or we just
drop the older GIT completely from moonbase.

In most of the other cases we (as in Lunar) go with whatever the source
code authors name their tarballs. Tell those authors to rename the tarballs
to all lowercase.

Terry Chan
-------------------------------------------------------------
On Fri, Jul 08, 2005 at 08:15:53AM -0700, 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