Not a bug.
This behavior goes way back to the Turn of the Century.
If you have:
MODULEPATH=/home/user/modules:/usr/etc/modules/common
And you have the files:
/home/user/modules/a/b
/usr/etc/modules/common/a/b
Only the first module "a/b" will be visible to the modules command.
I use this "FEATURE" all the time to test changes to existing modules.
(copy the module from the second path, to the first - then change an modify the copy and test it).
On 2025-08-22 5:17 AM, Laurent BESSON wrote:
> Hello dear Modules users,
>
> As an introduction, I have to say I did something weird : I have the same module name in 2 places and both are visible to < module > command.
>
> Of course, these 2 modules files have a different content. And I wanted to < forbid > one. So I added in a .modulerc the following line :
>
> module-forbid --message "This version has been removed" /media/TmpStore/users/lbesson/Tools/modulefiles/mentor/questa_lint/2025.2_1
>
> When I run < ml avail mentor/questa_lint>, it says (I include a screenshot to keep colors and nice display) :
>
> [cid:image001.png@01DC135D.46C53D90]
>
> It shows exactly the expected behaviour. But then I try to load the < available > one and I get this :
>
> [cid:image002.png@01DC135E.B4DE18A0]
>
> To me, it looks like a bug : I should be allowed to load < mentor/questa_lint/2025.2_1 > from < /tool/modules >
>
> What do you think ?
>
> Best regards,
> Laurent.
>
> PS : I'm running Modules 5.5 under RedHat machines
>
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
>
--
--------------------------------------------------------
The views and opinions expressed above are strictly
those of the author(s). The content of this message has
not been reviewed nor approved by any entity whatsoever.
--------------------------------------------------------
Paul FM Info: http://paulfm.com/~paulfm/
--------------------------------------------------------
|