Re: [libre-riscv-dev] gitlab-ci-archiver status

[Luke Kenneth Casson Leighton <lkcl@lkcl.net>]

ah i just realised, you may be tempted to assume that the outgoing command
is not 100% reliable and thus start writing retry and store and forward
code.

this is why i said assume the UNIX philosophy do one task and do it well.

other services do store and forward so use them.

we can always install exim4 as a relay.

so on consideration please use whatever wrapper rust puts around popen2 or
popen3, shove the log out on stdout, no command options (no env vars) where
the command is from the config file, no paramers, nothing.

it then becomes a 5 minute job to write a bash script "mail -s "build log"
fred@foo"

if the command does produce stderr output shove that into the error logs
and forget about it.

we need to get this handed over to alain and frieder as soon as possible.

this or equivalent will do

https://doc.rust-lang.org/1.8.0/libc/fn.popen.html

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev