Re: [libre-riscv-dev] Setup automation scripts

From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Setup automation scripts
Date: Wed, 25 Mar 2020 09:22:55 -0700
Message-ID: <CA8910BD-0AFF-43FF-ACEB-C3022F0A7258@getmailspring.com> (raw)
In-Reply-To: <CAPweEDxtmL-5in1Xeed90OMGyvxWSSB2TAum_xdAbrJprug-Hg@mail.gmail.com>

On Mar 25 2020, at 9:18 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> On Wed, Mar 25, 2020 at 4:04 PM Cole Poirier <colepoirier@gmail.com> wrote:
>> 
>> Hi Libre-SOC team,
>> 
>> I'm currently working on turning the setup Jacob and I did on his build
>> server into an easily replicable bash setup script. While working on
>> this yesterday, I concurrently tried to follow the hdl workflow, a
>> substantial part of which is setting up a debootstrapped chroot and
>> installing coriolis2. On this attempt I was finally able to complete it
>> (thanks to Luke and Jock for updating the process for Debian 10 and
>> working out a few other kinks in the process!),
> 
> hooraaay!
> 
>> but given the length and
>> complexity of this process, it strikes me as another candidate for
>> automation. I was thinking I could repeat the process I'm going through
>> with Jacob, working on the build server setup automation, with the HDL
>> workflow.
> 
> yep, sure, go for it.  drop all the commands into scripts, then...
> hmmm, you have git read/write access to the wiki: git commit them into
> HDL_workflow directory and put in a link to them in coriolis2.mdwn

Will do!

>> Jacob has advised me to set up a local debian vm for the
>> purposes of ensuring the script's reliability, so it is my thiniking
>> that it will be worthwhile to work on these two process automations concurrently.
>> Do you think that this is would be useful and worthwhile? Also, given
>> that we already have a hard dependency on python, are bash scripts
>> preferable to the python equivalent of these automation scripts?
> 
> python is total overkill, bash is generic and brain-dead.
> 
> there's absolutely no need for using python for this task, as there is
> zero interaction.  it's literally a matter of bang, bang, command,
> command.  remember you can output stuff to files with:
> 
> $ cat <<EOF > filename
> adasdjhasd
> asda
> sd
> EOF
> $
> 
> https://stackoverflow.com/questions/2500436/how-does-cat-eof-work-in-bash
> 
> so you absolutely do not need to use python, not even for file-writing.
> 
> l.

Perfect, thanks for the advice Luke. Working with you is a great
education in how to do software engineering properly.

Cole

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev