Also partly related to that feature:
I think it makes sense to include in the module whatis the list of extensions
in bundles, so people can query it with “module key”. We currently do that
manually, which is a pain…. Maybe I mention it already somewhere before?
Damian
On 23/01/17 10:49, "easy
Related to this:
Maybe it would be useful to add a small --dump-filter option, that simply dumps
a list of easyconfigs (or a directory tree with them), but applying filters for
it. For instance, if we want to share our setup, we might want to delete the
contact field. Likewise for site specific
On 01/20/17 20:17, Kenneth Hoste wrote:
> On 20/01/2017 10:10, Markus Geimer wrote:
>>> (unfortunately, I don't think EasyBuild has a tag for a "module load"
>>> message).
>> It should be fairly straightforward to support that as well (if
>> you want to hard-code this into the modulefile rather tha
: easybuild-requ...@lists.ugent.be
[mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Ward Poelmans
Sent: Friday, 20 January 2017 9:54 p.m.
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] LUA modules: whatis statement split up across multiple
lines when printed
On Thu, Jan 19, 2017 at 10:38
On 20/01/2017 10:49, Alvarez, Damian wrote:
I like it. I wanted actually to make PR including an extra “contact” field in
the easyconfig file (we currently have it simply included in the description),
but yours is way more complete.
+1, this sounds like a very well worked out proposal provi
On 20/01/2017 10:10, Markus Geimer wrote:
(unfortunately, I don't think EasyBuild has a tag for a "module load"
message).
It should be fairly straightforward to support that as well (if
you want to hard-code this into the modulefile rather than using
Lmod's admin.list approach).
This *is* al
Am I reading about one of the developments planned for the User Meeting?
On 20 January 2017 at 11:03, Markus Geimer wrote:
> On 01/20/17 10:49, Alvarez, Damian wrote:
> > I like it. I wanted actually to make PR including an extra “contact”
> > field in the easyconfig file (we currently have it s
On 01/20/17 10:49, Alvarez, Damian wrote:
> I like it. I wanted actually to make PR including an extra “contact”
> field in the easyconfig file (we currently have it simply included in
> the description), but yours is way more complete. However, just as a
> side note, empty fields should not be cre
I like it. I wanted actually to make PR including an extra “contact” field in
the easyconfig file (we currently have it simply included in the description),
but yours is way more complete. However, just as a side note, empty fields
should not be created. Having an “usage section” that is empty i
All,
>> I have noticed a slightly annoying (if small) side effect of the move
>> to lua module files. Specifically, module help and whatis statements
>> will now be split up across multiple lines if they are so formatted in
>> the easyconfig. An example follows at the end of this message.
>> [...]
On Thu, Jan 19, 2017 at 10:38 PM, Ben Roberts wrote:
> This is a problem for me and my site as we prepare our lists of modules by
> looking at the output of “module whatis”. While we could post-process that
> output, it is somewhat tedious and error prone to have to do so. The
> formatting may als
On 01/19/2017 03:38 PM, Ben Roberts wrote:
All,
I have noticed a slightly annoying (if small) side effect of the move
to lua module files. Specifically, module help and whatis statements
will now be split up across multiple lines if they are so formatted in
the easyconfig. An example follows
All,
I have noticed a slightly annoying (if small) side effect of the move to lua
module files. Specifically, module help and whatis statements will now be
split up across multiple lines if they are so formatted in the easyconfig.
An example follows at the end of this message.
This is a pro
13 matches
Mail list logo
