• Kirill Smelkov's avatar
    golang: Don't require users to put \ into gowork.install · 754acb1b
    Kirill Smelkov authored
    Previously it was required to put \ into multi-entry gowork.install,
    because the way it was processed was to directly pass it into bash
    command, and if \n were there the command was cut by bash and the
    trailing was considered as another command.
    
    We can avoid that by explicitly processing \n in gowork.install and
    translate it to just ' '. This helps people because now gowork.install
    becomes just a regular multiline buildout entry, similar e.g. to
    gowork.cpkgpath et all.
    
    Here is one example where it helps:
    
    jerome/slapos@95c45fe0 (comment 68408)
    
    /reviewed-by @jerome
    /reviewed-on nexedi/slapos!430
    754acb1b
Name
Last commit
Last update
..
gowork.cfg Loading commit data...
instance.cfg.in Loading commit data...
neotest-env.sh.in Loading commit data...
neotest-runTestSuite.in Loading commit data...
neotest.in Loading commit data...
software-dev.cfg Loading commit data...
software.cfg Loading commit data...