> On 29 Mar 2017, at 09:50, Alvarez, Damian <[email protected]> wrote:
> 
>    For easyconfig files specified on the command line, we don't check
>    anything, to give people the freedom to name their easyconfig files
>    "test.eb" or whatever (even the .eb extension isn't required).
> 
> 
> Yay!, freedom to shoot ourselves on the foot ;-P. IMO, if the robot can’t 
> pick it up, neither should eb when specifying it in the command line. That’s 
> at least how I’d configure our setup if that was an option.

+1! for a production setup. I do understand you may want to break the policy 
for testing purposes though ;)

@Kenneth: would it be possible to allow whatever filename for easyconfigs 
specified on the commandline, but do check for naming conventions and throw a 
big warning if the easyconfig cannot be picked up by the robot option for 
dependency resolution? We already have a perforated pair of feet here :o...

Cheers,

Pi

> Damian
> 
> 
> 
> 
> ------------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------------
> Forschungszentrum Juelich GmbH
> 52425 Juelich
> Sitz der Gesellschaft: Juelich
> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
> Prof. Dr. Sebastian M. Schmidt
> ------------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------------
> 

-------------------------------------------------------------
phone: +31 6 143 66 783
e-mail: [email protected]
skype:  pieter.online
-------------------------------------------------------------

Reply via email to