modules-interest — Discussion forum for modules usage.

Re: [Modules] Get variant of another module

[Xavier D. <xav...@gm...>]

The "is-loading" procedure exists but is not currently exposed in the
modulefile evaluation context. You may try to expose it with
"modulefile_extra_cmds" hook variable and see if it cope with your use
case.

The variant propagation method is a good one also. But I feel with
your message that the "goat" module is not compiler-specific so it may
not be semantically correct to have a compiler variant?

Best regards,
Xavier

Le mar. 24 déc. 2024 à 11:13, Adrien COTTE <adr...@as...> a écrit :
>
> Hi Xavier,
> Thank you for your quick response.
> Indeed, it works. I thought I had already tried that, but my case was slightly different, unfortunately.
> What about an "asked variant"? Perhaps an equivalent of "is-loading"?
> If goat/2.0 is a prerequisite for ziege/1.0, the "is-loaded" approach cannot work.
> Example:
> File: /usr/share/modulefiles/ziege/1.0
>
> #%Module
>
> set name "ziege"
> set version "1.0"
>
> variant compiler
>
> prereq goat/2.0
>
> File: /usr/share/modulefiles/goat/2.0
>
> #%Module
>
> set name "goat"
> set version "2.0"
>
> if { [is-loaded ziege compiler=gcc] } {
>     // does not work
> }
>
> The only solution I've found is to propagate variants across my modules.
> Updated Example:
> File: /usr/share/modulefiles/ziege/1.0
>
> #%Module
>
> set name "ziege"
> set version "1.0"
>
> variant compiler
>
> prereq goat/2.0 compiler=[getvariant compiler]
>
> File: /usr/share/modulefiles/goat/2.0
>
> #%Module
>
> set name "goat"
> set version "2.0"
>
> variant compiler
>
> if { [getvariant compiler] == gcc } {
>     // code
> }
>
> Let me know if you see any better way to handle this.
> Best regards,
> Adrien
> ________________________________
> De : Xavier Delaruelle <xav...@gm...>
> Envoyé : mardi 24 décembre 2024 09:52
> À : Environment Modules usage and discussion. <mod...@li...>
> Objet : Re: [Modules] Get variant of another module
>
> Hi Adrien,
>
> As far as I remind, there is no function that currently gives you the
> variants of a loaded module from another module, but you may try using
> the "is-loaded" command:
>
> if {[is-loaded ziege compiler=gcc]} {
>    // code
> } elseif {[is-loaded ziege compiler=llvm]}
>    ..
> }
>
> Best,
> Xavier
>
> Le mar. 24 déc. 2024 à 09:44, Adrien COTTE <adr...@as...> a écrit :
> >
> > Hi,
> >
> > Is it possible to get the variant of another module?
> >
> > A dummy example.
> >
> > $ module load ziege/1.0 compiler=gcc
> > $ module load goat/2.0
> >
> > In the goat/2.0 modulefile, I would like to check the ziege/1.0 compiler variant.
> >
> > Best,
> > Adrien Cotte
> > _______________________________________________
> > Modules-interest mailing list
> > Mod...@li...
> > https://lists.sourceforge.net/lists/listinfo/modules-interest
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Get variant of another module

[Adrien C. <adr...@as...>]

Hi Xavier,
Thank you for your quick response.
Indeed, it works. I thought I had already tried that, but my case was slightly different, unfortunately.
What about an "asked variant"? Perhaps an equivalent of "is-loading"?
If goat/2.0 is a prerequisite for ziege/1.0, the "is-loaded" approach cannot work.
Example:
File: /usr/share/modulefiles/ziege/1.0

#%Module

set name "ziege"
set version "1.0"

variant compiler

prereq goat/2.0


File: /usr/share/modulefiles/goat/2.0

#%Module

set name "goat"
set version "2.0"

if { [is-loaded ziege compiler=gcc] } {
    // does not work
}


The only solution I've found is to propagate variants across my modules.
Updated Example:
File: /usr/share/modulefiles/ziege/1.0

#%Module

set name "ziege"
set version "1.0"

variant compiler

prereq goat/2.0 compiler=[getvariant compiler]


File: /usr/share/modulefiles/goat/2.0

#%Module

set name "goat"
set version "2.0"

variant compiler

if { [getvariant compiler] == gcc } {
    // code
}


Let me know if you see any better way to handle this.
Best regards,
Adrien
________________________________
De : Xavier Delaruelle <xav...@gm...>
Envoyé : mardi 24 décembre 2024 09:52
À : Environment Modules usage and discussion. <mod...@li...>
Objet : Re: [Modules] Get variant of another module

Hi Adrien,

As far as I remind, there is no function that currently gives you the
variants of a loaded module from another module, but you may try using
the "is-loaded" command:

if {[is-loaded ziege compiler=gcc]} {
   // code
} elseif {[is-loaded ziege compiler=llvm]}
   ..
}

Best,
Xavier

Le mar. 24 déc. 2024 à 09:44, Adrien COTTE <adr...@as...> a écrit :
>
> Hi,
>
> Is it possible to get the variant of another module?
>
> A dummy example.
>
> $ module load ziege/1.0 compiler=gcc
> $ module load goat/2.0
>
> In the goat/2.0 modulefile, I would like to check the ziege/1.0 compiler variant.
>
> Best,
> Adrien Cotte
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest


_______________________________________________
Modules-interest mailing list
Mod...@li...
https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Get variant of another module

[Xavier D. <xav...@gm...>]

Hi Adrien,

As far as I remind, there is no function that currently gives you the
variants of a loaded module from another module, but you may try using
the "is-loaded" command:

if {[is-loaded ziege compiler=gcc]} {
   // code
} elseif {[is-loaded ziege compiler=llvm]}
   ..
}

Best,
Xavier

Le mar. 24 déc. 2024 à 09:44, Adrien COTTE <adr...@as...> a écrit :
>
> Hi,
>
> Is it possible to get the variant of another module?
>
> A dummy example.
>
> $ module load ziege/1.0 compiler=gcc
> $ module load goat/2.0
>
> In the goat/2.0 modulefile, I would like to check the ziege/1.0 compiler variant.
>
> Best,
> Adrien Cotte
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

[Modules] Get variant of another module

[Adrien C. <adr...@as...>]

Hi,

Is it possible to get the variant of another module?

A dummy example.

$ module load ziege/1.0 compiler=gcc
$ module load goat/2.0

In the goat/2.0 modulefile, I would like to check the ziege/1.0 compiler variant.

Best,
Adrien Cotte

Re: [Modules] Testing initrc

[Xavier D. <xav...@gm...>]

Hello Baudilio,

I suggest to use a Unix group to distinguish the users that may test
the code, then sourcing this test file in etc/initrc if user is part
of this group:

if {[module-info usergroups group_name]} {
    source /path/to/etc/nitric.TEST
}

I take the opportunity of this message to wish everyone a merry christmas.

Best regards,
Xavier

Le mar. 24 déc. 2024 à 01:57, Baudilio Tejerina - NOAA Affiliate via
Modules-interest <mod...@li...> a écrit :
>
> Hello.
>
> I need to add the following logic to the etc/initrc file.
> Before putting the codeI in production, I have created the file etc/nitric.TEST also located in etc/
>
>
> switch -regexp -matchvar name -- $tcl_platform(osVersion) {
>     {el8} {
> module use --append {/this/path8}
>     }
>     {el7} {
>     module use --append {/this/path7}
>     }
> }
>
>
> Is there a way a user could test it instead of parsing the current etc/initrc?
>
> Thank You!
>
> Baudilio
>
>
>
> Baudilio Tejerina, Ph. D. (Theoretical Physics and Chemistry)
> NOAA Geophysical Fluid Dynamics Laboratory
> Forrestal Campus, Princeton University
> 201 Forrestal Rd., 164
> Princeton, NJ - 08540
> _______________________________
> GPG Key ID: 72668D3DD3D71B44
> ☎: (609) 452 5839
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

[Modules] Testing initrc

[Baudilio T. - N. A. <bau...@no...>]

Hello.

I need to add the following logic to the etc/initrc file.
Before putting the codeI in production, I have created the file etc/nitric.TEST also located in etc/


switch -regexp -matchvar name -- $tcl_platform(osVersion) {
    {el8} {
	module use --append {/this/path8}
    }
    {el7} {
    	module use --append {/this/path7}
    }
}


Is there a way a user could test it instead of parsing the current etc/initrc?

Thank You!

Baudilio



Baudilio Tejerina, Ph. D. (Theoretical Physics and Chemistry)
NOAA Geophysical Fluid Dynamics Laboratory
Forrestal Campus, Princeton University
201 Forrestal Rd., 164
Princeton, NJ - 08540
_______________________________
GPG Key ID: 72668D3DD3D71B44
☎: (609) 452 5839

[Modules] Development documentation improvement

[Xavier D. <xav...@gm...>]

Dear All,

I would like to let you know that I have improved the development
documentation of the project in several ways:

* add Developer HowTo (to understand how to add config option/module
sub-command or how a new Modules release is created) [1]
* create an acknowledgment page for former project leads [2]
* write Modules project governance [3] to clarify how this project is
currently organized

Do not hesitate to comment, provide suggestion on that. You are welcome.

Best regards,
Xavier

[1] https://modules.readthedocs.io/en/latest/devel.html
[2] https://modules.readthedocs.io/en/latest/acknowledgments.html
[3] https://modules.readthedocs.io/en/latest/GOVERNANCE.html

[Modules] Modules repository is moving!

[Xavier D. <xav...@gm...>]

Dear All,

Modules repository is moving! It will now be available at
https://github.com/envmodules/modules but don't panic old links will
still be valid.

The project is aiming at a neutral home, here named "envmodules", that
also reflects the name handle used on social media platforms.

This move does not change a thing regarding CEA support to the
project. Many thanks to CEA for its support during the past years.

Regards,
Xavier

Re: [Modules] How to set-env with multi line content

[Byron B. <byr...@pr...>]

Perfect! I’ll give that a try! Thank you, Xavier and Paul.

Byron Boulton

On Tue, Dec 3, 2024 at 10:25 PM, Xavier Delaruelle <[xav...@gm...](mailto:On Tue, Dec 3, 2024 at 10:25 PM, Xavier Delaruelle <<a href=)> wrote:

> The full module may look like:
>
> #%Module
> if {[module-info mode load]} {
> switch -- [module-info shelltype] {
> sh {puts stdout "FOO='my\nmulti\nline\nvalue'; export FOO;"}
> }
> } elseif {[module-info mode unload]} {
> unsetenv --unset-on-unload FOO
> }
>
> Regards,
> Xavier
>
> Le mar. 3 déc. 2024 à 23:53, Paul Markfort <pau...@gm...> a écrit :
>>
>>
>> A little complicatesd; but, you should be able to figure this out for yourself:
>>
>> Read the MAN page for modulefile
>> man modulefile
>>
>> The section you want is about module-info
>>
>> Specifically this:
>> module-info mode [modetype]
>>
>>
>> The if statement is similar to the way I used module-info shell
>> You might put this new test inside the module-info shell test (or maybe outside, depending on what you want).
>>
>> You need to decide which module modes need an action - and what action you want for each.
>>
>> Obviously, for the "load" mode you want the puts statement.
>>
>>
>> On 2024-12-03 4:33 PM, Byron Boulton via Modules-interest wrote:
>> > Oh good point. I think people on our system are only using modules with bash and maybe zsh, but I should wrap it.
>> >
>> > Any idea if I can put something in the module file to undo setting the environment variable when someone runs “ml unload”?
>> >
>> > Byron Boulton
>> >
>> > Sent from [Proton Mail](https://proton.me/mail/home) for iOS
>> >
>> > On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <[pau...@gm...](mailto:On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <<a href=)> wrote:
>> >
>> >> You might want to surround that code to make sure it is only run for bash.
>> >>
>> >> if { [module-info shell bash] } {
>> >> puts stdout "export FOO='my\nmulti\nline\nvalue';"
>> >> }
>> >>
>> >> Note:
>> >> The real sh (bourne shell) doesn't allow export to set values inline.
>> >> However, on linux, sh is actually bash (usually).
>> >>
>> >> On 2024-12-03 1:59 PM, Xavier Delaruelle wrote:
>> >>> Hello Byron,
>> >>>
>> >>> Setting a multi-line value to an environment variable with "setenv" is
>> >>> not possible with current version of Modules. I will look at
>> >>> implementing such feature.
>> >>>
>> >>> As a workaround, you may use the "puts" command to craft the shell
>> >>> command to define variable with such specific value:
>> >>>
>> >>> #%Module
>> >>> puts stdout "export FOO='my\nmulti\nline\nvalue';"
>> >>>
>> >>> Regards,
>> >>> Xavier
>> >>>
>> >>> Le mar. 3 déc. 2024 à 15:16, Byron Boulton via Modules-interest
>> >>> <mod...@li...> a écrit :
>> >>>>
>> >>>> I need to set-env a variable with contents from a file. In bash I can do this with
>> >>>>
>> >>>> export FOO="$(cat /home/username/foofile.dat)"
>> >>>>
>> >>>> So far I tried various permutations like
>> >>>>
>> >>>> set fp [open "/home/username/foofile.dat"]
>> >>>> set file_data [read $fp]
>> >>>> close $fp
>> >>>> set-env FOO "$file_data"
>> >>>>
>> >>>> But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.
>> >>>>
>> >>>> Does anyone have ideas on how I can set a multiline variable from the contents of a file?
>> >>>>
>> >>>> (Some keywords for future searchability in the archives: multiline, multi-line, newline)
>> >>>>
>> >>>> Byron
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> 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/
>> >> --------------------------------------------------------
>> >>
>> >> _______________________________________________
>> >> Modules-interest mailing list
>> >> Mod...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/modules-interest
>> >>
>> >>
>> >> _______________________________________________
>> >> 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/
>> --------------------------------------------------------
>>
>>
>> _______________________________________________
>> Modules-interest mailing list
>> Mod...@li...
>> https://lists.sourceforge.net/lists/listinfo/modules-interest
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] How to set-env with multi line content

[Xavier D. <xav...@gm...>]

The full module may look like:

#%Module
if {[module-info mode load]} {
    switch -- [module-info shelltype] {
        sh {puts stdout "FOO='my\nmulti\nline\nvalue'; export FOO;"}
    }
} elseif {[module-info mode unload]} {
    unsetenv --unset-on-unload FOO
}

Regards,
Xavier

Le mar. 3 déc. 2024 à 23:53, Paul Markfort <pau...@gm...> a écrit :
>
>
> A little complicatesd; but, you should be able to figure this out for yourself:
>
> Read the MAN page for modulefile
>         man modulefile
>
> The section you want is about module-info
>
> Specifically this:
>         module-info mode [modetype]
>
>
> The if statement is similar to the way I used module-info shell
> You might put this new test inside the module-info shell test (or maybe outside, depending on what you want).
>
> You need to decide which module modes need an action - and what action you want for each.
>
> Obviously, for the "load" mode you want the puts statement.
>
>
> On 2024-12-03 4:33 PM, Byron Boulton via Modules-interest wrote:
> > Oh good point. I think people on our system are only using modules with bash and maybe zsh, but I should wrap it.
> >
> > Any idea if I can put something in the module file to undo setting the environment variable when someone runs “ml unload”?
> >
> > Byron Boulton
> >
> > Sent from [Proton Mail](https://proton.me/mail/home) for iOS
> >
> > On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <[pau...@gm...](mailto:On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <<a href=)> wrote:
> >
> >> You might want to surround that code to make sure it is only run for bash.
> >>
> >> if { [module-info shell bash] } {
> >> puts stdout "export FOO='my\nmulti\nline\nvalue';"
> >> }
> >>
> >> Note:
> >> The real sh (bourne shell) doesn't allow export to set values inline.
> >> However, on linux, sh is actually bash (usually).
> >>
> >> On 2024-12-03 1:59 PM, Xavier Delaruelle wrote:
> >>> Hello Byron,
> >>>
> >>> Setting a multi-line value to an environment variable with "setenv" is
> >>> not possible with current version of Modules. I will look at
> >>> implementing such feature.
> >>>
> >>> As a workaround, you may use the "puts" command to craft the shell
> >>> command to define variable with such specific value:
> >>>
> >>> #%Module
> >>> puts stdout "export FOO='my\nmulti\nline\nvalue';"
> >>>
> >>> Regards,
> >>> Xavier
> >>>
> >>> Le mar. 3 déc. 2024 à 15:16, Byron Boulton via Modules-interest
> >>> <mod...@li...> a écrit :
> >>>>
> >>>> I need to set-env a variable with contents from a file. In bash I can do this with
> >>>>
> >>>> export FOO="$(cat /home/username/foofile.dat)"
> >>>>
> >>>> So far I tried various permutations like
> >>>>
> >>>> set fp [open "/home/username/foofile.dat"]
> >>>> set file_data [read $fp]
> >>>> close $fp
> >>>> set-env FOO "$file_data"
> >>>>
> >>>> But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.
> >>>>
> >>>> Does anyone have ideas on how I can set a multiline variable from the contents of a file?
> >>>>
> >>>> (Some keywords for future searchability in the archives: multiline, multi-line, newline)
> >>>>
> >>>> Byron
> >>>
> >>>
> >>> _______________________________________________
> >>> 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/
> >> --------------------------------------------------------
> >>
> >> _______________________________________________
> >> Modules-interest mailing list
> >> Mod...@li...
> >> https://lists.sourceforge.net/lists/listinfo/modules-interest
> >>
> >>
> >> _______________________________________________
> >> 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/
> --------------------------------------------------------
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] How to set-env with multi line content

[Paul M. <pau...@gm...>]

A little complicatesd; but, you should be able to figure this out for yourself:

Read the MAN page for modulefile
	man modulefile

The section you want is about module-info

Specifically this:
	module-info mode [modetype]


The if statement is similar to the way I used module-info shell
You might put this new test inside the module-info shell test (or maybe outside, depending on what you want).

You need to decide which module modes need an action - and what action you want for each.

Obviously, for the "load" mode you want the puts statement.


On 2024-12-03 4:33 PM, Byron Boulton via Modules-interest wrote:
> Oh good point. I think people on our system are only using modules with bash and maybe zsh, but I should wrap it.
> 
> Any idea if I can put something in the module file to undo setting the environment variable when someone runs “ml unload”?
> 
> Byron Boulton
> 
> Sent from [Proton Mail](https://proton.me/mail/home) for iOS
> 
> On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <[pau...@gm...](mailto:On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <<a href=)> wrote:
> 
>> You might want to surround that code to make sure it is only run for bash.
>>
>> if { [module-info shell bash] } {
>> puts stdout "export FOO='my\nmulti\nline\nvalue';"
>> }
>>
>> Note:
>> The real sh (bourne shell) doesn't allow export to set values inline.
>> However, on linux, sh is actually bash (usually).
>>
>> On 2024-12-03 1:59 PM, Xavier Delaruelle wrote:
>>> Hello Byron,
>>>
>>> Setting a multi-line value to an environment variable with "setenv" is
>>> not possible with current version of Modules. I will look at
>>> implementing such feature.
>>>
>>> As a workaround, you may use the "puts" command to craft the shell
>>> command to define variable with such specific value:
>>>
>>> #%Module
>>> puts stdout "export FOO='my\nmulti\nline\nvalue';"
>>>
>>> Regards,
>>> Xavier
>>>
>>> Le mar. 3 déc. 2024 à 15:16, Byron Boulton via Modules-interest
>>> <mod...@li...> a écrit :
>>>>
>>>> I need to set-env a variable with contents from a file. In bash I can do this with
>>>>
>>>> export FOO="$(cat /home/username/foofile.dat)"
>>>>
>>>> So far I tried various permutations like
>>>>
>>>> set fp [open "/home/username/foofile.dat"]
>>>> set file_data [read $fp]
>>>> close $fp
>>>> set-env FOO "$file_data"
>>>>
>>>> But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.
>>>>
>>>> Does anyone have ideas on how I can set a multiline variable from the contents of a file?
>>>>
>>>> (Some keywords for future searchability in the archives: multiline, multi-line, newline)
>>>>
>>>> Byron
>>>
>>>
>>> _______________________________________________
>>> 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/
>> --------------------------------------------------------
>>
>> _______________________________________________
>> Modules-interest mailing list
>> Mod...@li...
>> https://lists.sourceforge.net/lists/listinfo/modules-interest
>>
>>
>> _______________________________________________
>> 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/
--------------------------------------------------------

Re: [Modules] How to set-env with multi line content

[Byron B. <byr...@pr...>]

Oh good point. I think people on our system are only using modules with bash and maybe zsh, but I should wrap it.

Any idea if I can put something in the module file to undo setting the environment variable when someone runs “ml unload”?

Byron Boulton

Sent from [Proton Mail](https://proton.me/mail/home) for iOS

On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <[pau...@gm...](mailto:On Tue, Dec 3, 2024 at 4:13 PM, Paul Markfort <<a href=)> wrote:

> You might want to surround that code to make sure it is only run for bash.
>
> if { [module-info shell bash] } {
> puts stdout "export FOO='my\nmulti\nline\nvalue';"
> }
>
> Note:
> The real sh (bourne shell) doesn't allow export to set values inline.
> However, on linux, sh is actually bash (usually).
>
> On 2024-12-03 1:59 PM, Xavier Delaruelle wrote:
>> Hello Byron,
>>
>> Setting a multi-line value to an environment variable with "setenv" is
>> not possible with current version of Modules. I will look at
>> implementing such feature.
>>
>> As a workaround, you may use the "puts" command to craft the shell
>> command to define variable with such specific value:
>>
>> #%Module
>> puts stdout "export FOO='my\nmulti\nline\nvalue';"
>>
>> Regards,
>> Xavier
>>
>> Le mar. 3 déc. 2024 à 15:16, Byron Boulton via Modules-interest
>> <mod...@li...> a écrit :
>>>
>>> I need to set-env a variable with contents from a file. In bash I can do this with
>>>
>>> export FOO="$(cat /home/username/foofile.dat)"
>>>
>>> So far I tried various permutations like
>>>
>>> set fp [open "/home/username/foofile.dat"]
>>> set file_data [read $fp]
>>> close $fp
>>> set-env FOO "$file_data"
>>>
>>> But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.
>>>
>>> Does anyone have ideas on how I can set a multiline variable from the contents of a file?
>>>
>>> (Some keywords for future searchability in the archives: multiline, multi-line, newline)
>>>
>>> Byron
>>
>>
>> _______________________________________________
>> 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/
> --------------------------------------------------------
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] How to set-env with multi line content

[Paul M. <pau...@gm...>]

You might want to surround that code to make sure it is only run for bash.

if { [module-info shell bash] } {
	puts stdout "export FOO='my\nmulti\nline\nvalue';"
}


Note:
The real sh (bourne shell) doesn't allow export to set values inline.
However, on linux, sh is actually bash (usually).



On 2024-12-03 1:59 PM, Xavier Delaruelle wrote:
> Hello Byron,
> 
> Setting a multi-line value to an environment variable with "setenv" is
> not possible with current version of Modules. I will look at
> implementing such feature.
> 
> As a workaround, you may use the "puts" command to craft the shell
> command to define variable with such specific value:
> 
> #%Module
> puts stdout "export FOO='my\nmulti\nline\nvalue';"
> 
> Regards,
> Xavier
> 
> Le mar. 3 déc. 2024 à 15:16, Byron Boulton via Modules-interest
> <mod...@li...> a écrit :
>>
>> I need to set-env a variable with contents from a file. In bash I can do this with
>>
>>      export FOO="$(cat /home/username/foofile.dat)"
>>
>> So far I tried various permutations like
>>
>>      set fp [open "/home/username/foofile.dat"]
>>      set file_data [read $fp]
>>      close $fp
>>      set-env FOO "$file_data"
>>
>> But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.
>>
>> Does anyone have ideas on how I can set a multiline variable from the contents of a file?
>>
>> (Some keywords for future searchability in the archives: multiline, multi-line, newline)
>>
>> Byron
> 
> 
> _______________________________________________
> 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/
--------------------------------------------------------

Re: [Modules] How to set-env with multi line content

[Byron B. <byr...@pr...>]

If I use a puts command to set the variable, is there a way to have the module unset that value when I run module unload?

Byron Boulton

On Tue, Dec 3, 2024 at 2:59 PM, Xavier Delaruelle <[xav...@gm...](mailto:On Tue, Dec 3, 2024 at 2:59 PM, Xavier Delaruelle <<a href=)> wrote:

> Hello Byron,
>
> Setting a multi-line value to an environment variable with "setenv" is
> not possible with current version of Modules. I will look at
> implementing such feature.
>
> As a workaround, you may use the "puts" command to craft the shell
> command to define variable with such specific value:
>
> #%Module
> puts stdout "export FOO='my\nmulti\nline\nvalue';"
>
> Regards,
> Xavier
>
> Le mar. 3 déc. 2024 à 15:16, Byron Boulton via Modules-interest
> <mod...@li...> a écrit :
>>
>> I need to set-env a variable with contents from a file. In bash I can do this with
>>
>> export FOO="$(cat /home/username/foofile.dat)"
>>
>> So far I tried various permutations like
>>
>> set fp [open "/home/username/foofile.dat"]
>> set file_data [read $fp]
>> close $fp
>> set-env FOO "$file_data"
>>
>> But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.
>>
>> Does anyone have ideas on how I can set a multiline variable from the contents of a file?
>>
>> (Some keywords for future searchability in the archives: multiline, multi-line, newline)
>>
>> Byron
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] How to set-env with multi line content

[Xavier D. <xav...@gm...>]

Hello Byron,

Setting a multi-line value to an environment variable with "setenv" is
not possible with current version of Modules. I will look at
implementing such feature.

As a workaround, you may use the "puts" command to craft the shell
command to define variable with such specific value:

#%Module
puts stdout "export FOO='my\nmulti\nline\nvalue';"

Regards,
Xavier

Le mar. 3 déc. 2024 à 15:16, Byron Boulton via Modules-interest
<mod...@li...> a écrit :
>
> I need to set-env a variable with contents from a file. In bash I can do this with
>
>     export FOO="$(cat /home/username/foofile.dat)"
>
> So far I tried various permutations like
>
>     set fp [open "/home/username/foofile.dat"]
>     set file_data [read $fp]
>     close $fp
>     set-env FOO "$file_data"
>
> But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.
>
> Does anyone have ideas on how I can set a multiline variable from the contents of a file?
>
> (Some keywords for future searchability in the archives: multiline, multi-line, newline)
>
> Byron

[Modules] How to set-env with multi line content

[Byron B. <byr...@pr...>]

I need to set-env a variable with contents from a file. In bash I can do this with

export FOO="$(cat /home/username/foofile.dat)"

So far I tried various permutations like

set fp [open "/home/username/foofile.dat"]
set file_data [read $fp]
close $fp
set-env FOO "$file_data"

But I always end up with a “command not found” message from bash trying to evaluate the second line of the file. This shows me that the module load must outputting a string to bash that is only setting the first line of the file to the variable FOO, then the subsequent file lines are getting dropped right to bash to evaluate.

Does anyone have ideas on how I can set a multiline variable from the contents of a file?

(Some keywords for future searchability in the archives: multiline, multi-line, newline)

Byron

Re: [Modules] Using linux command in module file

[Patrick B. <Pat...@un...>]

Thank you Laurent for the quick answer. I'm not familiar with tcl 
language and I was not aware of this syntax!
I've juste moved the loading of the required modules in a "prereq-all" 
directive and all is running as expected with your suggestion. So, 
changing a required module update "automagically" the setup.

Patrick

Le 27/11/2024 à 10:30, Laurent BESSON a écrit :
>
> Hello Patrick
>
> Module syntax is in tcl. So, if I understand correctly your need, I 
> would write something like
>
> setenv IRL_DIR [exec pkg-config --variable=prefix irl_fortran]
>
> Best regards,
>
> Laurent BESSON
>
> -----Message d'origine-----
> De : Patrick Begou <Pat...@un...>
> Envoyé : mercredi 27 novembre 2024 10:05
> À : mod...@li...
> Objet : [Modules] Using linux command in module file
>
> Hi,
>
> this is my first post on the list. I'm using module environment for a 
> while, but I'm stuck to create a module for a specific software.
>
> The sotfware requires some additional libraries managed with module 
> environment so, for example, in my user module file I use:
>
> if [ module-info mode load ] {
>
>    module load GCC14/irl-2024.11.26
>
>   }
>
> to load this required irl-2024.11.26 module which is system wide.
>
> Then, in my user's module file, I need to set a variable based on the 
> environment set up with the above module. With bash I would write:
>
> IRL_DIR=$(pkg-config --variable=prefix irl_fortran)
>
> as the pkg-config path has been setup when loading the
>
> GCC14/irl-2024.11.26 module.
>
> Is there a way to do this in my module file to ensure that the IRL_DIR 
> variable will be set dynamicaly and correctly with the irl loaded module ?
>
> Thank you for your advices.
>
> Patrick
>
> _______________________________________________
>
> Modules-interest mailing list
>
> Mod...@li... 
> <mailto:Mod...@li...>
>
> https://lists.sourceforge.net/lists/listinfo/modules-interest 
> <https://lists.sourceforge.net/lists/listinfo/modules-interest>
>
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest

Re: [Modules] Using linux command in module file

[Laurent B. <lau...@ea...>]

Hello Patrick



Module syntax is in tcl. So, if I understand correctly your need, I would write something like



setenv IRL_DIR [exec pkg-config --variable=prefix irl_fortran]





Best regards,

Laurent BESSON





-----Message d'origine-----
De : Patrick Begou <Pat...@un...>
Envoyé : mercredi 27 novembre 2024 10:05
À : mod...@li...
Objet : [Modules] Using linux command in module file



Hi,



this is my first post on the list. I'm using module environment for a while, but I'm stuck to create a module for a specific software.



The sotfware requires some additional libraries managed with module environment so, for example, in my user module file I use:

if [ module-info mode load ] {

   module load GCC14/irl-2024.11.26

  }



to load this required irl-2024.11.26 module which is system wide.





Then, in my user's module file, I need to set a variable based on the environment set up with the above module. With bash I would write:



IRL_DIR=$(pkg-config --variable=prefix irl_fortran)



as the pkg-config path has been setup when loading the

GCC14/irl-2024.11.26 module.



Is there a way to do this in my module file to ensure that the IRL_DIR variable will be set dynamicaly and correctly with the irl loaded module ?



Thank you for your advices.



Patrick







_______________________________________________

Modules-interest mailing list

Mod...@li...<mailto:Mod...@li...>

https://lists.sourceforge.net/lists/listinfo/modules-interest

[Modules] Using linux command in module file

[Patrick B. <Pat...@un...>]

Hi,

this is my first post on the list. I'm using module environment for a 
while, but I'm stuck to create a module for a specific software.

The sotfware requires some additional libraries managed with module 
environment so, for example, in my user module file I use:
if [ module-info mode load ] {
    module load GCC14/irl-2024.11.26
   }

to load this required irl-2024.11.26 module which is system wide.


Then, in my user's module file, I need to set a variable based on the 
environment set up with the above module. With bash I would write:

IRL_DIR=$(pkg-config --variable=prefix irl_fortran)

as the pkg-config path has been setup when loading the 
GCC14/irl-2024.11.26 module.

Is there a way to do this in my module file to ensure that the IRL_DIR 
variable will be set dynamicaly and correctly with the irl loaded module ?

Thank you for your advices.

Patrick

[Modules] Environment Modules on Bluesky

[Xavier D. <xav...@gm...>]

Hello All,

I would like to let you know that I have created an account for
Modules project on the Bluesky social media. The account is
@envmodules.bsky.social. Like for Twitter/X and Mastodon, I will share
news of the project on this platform.

Cheers,
Xavier

Re: [Modules] SC24

[Xavier D. <xav...@gm...>]

If you want a broader view on the available "module" implementations,
Robert McLay is also participating to SC24 and he will talk about Lmod
on TACC booth (1203) on Wednesday at 2pm.

Cheers,
Xavier

Le dim. 17 nov. 2024 à 16:22, Xavier Delaruelle
<xav...@gm...> a écrit :
>
> Hi All,
>
> I am participating to SC24. I will be on CEA booth (#4143) on
> Wednesday 20th at 11am.
>
> I have cooked some examples to demonstrate new and upcoming features
> of Modules. It will also be a good opportunity to chat or if you have
> some specific question.
>
> There will also be some Modules stickers to grab :-).
>
> Cheers,
> Xavier

[Modules] SC24

[Xavier D. <xav...@gm...>]

Hi All,

I am participating to SC24. I will be on CEA booth (#4143) on
Wednesday 20th at 11am.

I have cooked some examples to demonstrate new and upcoming features
of Modules. It will also be a good opportunity to chat or if you have
some specific question.

There will also be some Modules stickers to grab :-).

Cheers,
Xavier

Re: [Modules] Modules 5.5.0 released

[Xavier D. <xav...@gm...>]

Hello All,

I am taking the opportunity of the Modules 5.5 release to announce
that I am starting my self-company, XaDev, in addition to my primary
job. This new activity will be about developing specific features on
Modules, providing expertise to deploy and setup the tool to fit your
needs, etc.

Do not hesitate to contact me if you want to exchange on some needs
and get a quote.

If you just want to support my regular work on the Modules project,
you can now sponsor me on GitHub:

https://github.com/sponsors/xdelaruelle

Best regards,
Xavier

Le lun. 11 nov. 2024 à 14:03, Xavier Delaruelle
<xav...@gm...> a écrit :
>
> Hello All,
>
> I am thrilled to announce that Modules 5.5 is out! Many new features
> have been added, the most prominent are: Logging activity, Negating
> extra match search criteria, PowerShell support, Specific modulepath
> for requirements, Conflict unload and Improved automated module
> handling mechanisms.
>
> Details on the major changes included in this new release are provided
> in the MIGRATING document. The list of all changes made in this new
> version are described in the NEWS document.
>
>  http://modules.readthedocs.io/en/stable/MIGRATING.html
>  http://modules.readthedocs.io/en/stable/NEWS.html
>
> The tarball of this new version can be downloaded at:
>
>  http://downloads.sourceforge.net/modules/modules-5.5.0.tar.gz
>
> The zipball to install this new version on Windows platform can be
> downloaded at:
>
>  http://downloads.sourceforge.net/modules/modules-5.5.0-win.zip
>
> If you encounter any issue, please let us know by creating a ticket on
> the project bug tracker at:
>
>  https://github.com/cea-hpc/modules/issues
>
> Many thanks to Laurent Besson, Robert McLay and Simon Lukas Märtens
> for their contribution to this release. Many thanks also to all of you
> who improve Modules by reporting bugs or sharing new ideas.
>
> Best regards,
> Xavier

[Modules] Modules 5.5.0 released

[Xavier D. <xav...@gm...>]

Hello All,

I am thrilled to announce that Modules 5.5 is out! Many new features
have been added, the most prominent are: Logging activity, Negating
extra match search criteria, PowerShell support, Specific modulepath
for requirements, Conflict unload and Improved automated module
handling mechanisms.

Details on the major changes included in this new release are provided
in the MIGRATING document. The list of all changes made in this new
version are described in the NEWS document.

 http://modules.readthedocs.io/en/stable/MIGRATING.html
 http://modules.readthedocs.io/en/stable/NEWS.html

The tarball of this new version can be downloaded at:

 http://downloads.sourceforge.net/modules/modules-5.5.0.tar.gz

The zipball to install this new version on Windows platform can be
downloaded at:

 http://downloads.sourceforge.net/modules/modules-5.5.0-win.zip

If you encounter any issue, please let us know by creating a ticket on
the project bug tracker at:

 https://github.com/cea-hpc/modules/issues

Many thanks to Laurent Besson, Robert McLay and Simon Lukas Märtens
for their contribution to this release. Many thanks also to all of you
who improve Modules by reporting bugs or sharing new ideas.

Best regards,
Xavier

[Modules] Specific modulepath for requirements

[Xavier D. <xav...@gm...>]

Dear All,

Last feature addition for upcoming v5.5: the introduction of a
--modulepath option on the always-load, depends-on, prereq, prereq-all
and prereq-any modulefile commands.

This new option indicates that requirement should be specifically
searched in the provided list of modulepaths. Such mechanism helps to
ensure loaded requirements are those expected and they are not coming
from an unexpected module tree.

See examples at:
https://modules.readthedocs.io/en/latest/MIGRATING.html#specific-modulepath-for-requirements

Regards,
Xavier