Difference: UnixShellSupport (1 vs. 2)

Revision 22019-04-24 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
During the LHCb Core Software meeting of the 12/12/2018 (https://indico.cern.ch/event/779237/), in view of the upcoming deployment of the new environment configuration tool LbEnv, the following policy was decided:
Line: 12 to 12
 
  • Support for bourne compatible shells such as zsh will be done on a best effort basis
    • We will avoid using really bash-specifics constructs
Changed:
<
<
    • we will eely on users to come to us with merge requests as we will not investigate all shells
>
>
    • we will rely on users to come to us with merge requests as we will not investigate all shells
 

-- BenjaminCouturier - 2018-12-12

Revision 12018-12-12 - BenjaminCouturier

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbComputing"
During the LHCb Core Software meeting of the 12/12/2018 (https://indico.cern.ch/event/779237/), in view of the upcoming deployment of the new environment configuration tool LbEnv, the following policy was decided:

  • bash is the officially supported shell
    • It should be used for production jobs
    • It will be used in all environment tools integration/regression tests

  • tcsh support of the existing code will be done on a best effort basis, i.e. when time allows and not critical
    • New features will not be ported
    • Deprecation warnings will be added to LbEnv when sourcing from tcsh

  • Support for bourne compatible shells such as zsh will be done on a best effort basis
    • We will avoid using really bash-specifics constructs
    • we will eely on users to come to us with merge requests as we will not investigate all shells

-- BenjaminCouturier - 2018-12-12

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback