|
From: Leo B. <lb...@br...> - 2001-07-13 04:05:44
|
"R.K. Owen Ph.D." <rk...@ow...> wrote: > > > The purpose of this latest version, was to fix all the known > > > bugs > > [more snippage] > > At least known by me. Sorry to say, I did not look at the > SourceForge bug tracker items. I'm just used to looking at bugs > submitted to this list. I'll have to figure out how to get > SourceForge to email me when new bugs are submitted. Hello, Dr. Owen. No worries; it wasn't a deadly bug by any means, otherwise I would have posted to the list as well. > > I posted a bug in the Sourceforge problem report area last week; > > do those postings generate an email to you and/or Robert Minsk? > > I thought to send a message to the list, but I thought it would > > be redundant. > > I just noticed it now. However, there were no .version files in the > download tar ball. If the problem persists, and it's not related > to deep directories, then upload them again with the .version files. > I'll try to fix it. I've sent the file separately. > > > Now it comes to the heart of the matter. There have been some > > > requests to fix modules to handle deep modulefile directories > > > with regards to version files, etc.. > > > > [snip] > > > > I wish I had something intelligent to offer on this, but it's > > so unnecessary in our usage of modules that it's a don't-care > > to me... I wonder if any of the requestors of the feature might > > be able to expand on their usage model so this lost soul could > > better understand the need for these changes? I hate it when > > my clue meter isn't registering... > > I like to group my modules into categories. For example, > browsers/netscape/4.61, browsers/netscape/6.0, browsers/opera/4.0, etc. > and what happens is that the .version files don't get read. Say > browsers/netscape/.version points to 4.61 which is totally ignored and > netscape/6.0 will be loaded if doing "module load browsers/netscape" Thank you for spelling it out for me. It makes perfect sense. > We really could use someone to put up web pages up on > modules.sourceforge.net. If I do it, then the pages will > turn out rather bland. I'd be happy to take a stab at it; I do some HTML both at home and work so I'm at least above the clueless level there. Okay, a little better than that even. Throw some requirements my way (content, example of good sourceforge page to look at, etc.) and I'll get started. > Thanks for the input, Likewise! - Leo Butler |
