Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] Setup automation scripts
Date: Wed, 25 Mar 2020 09:04:43 -0700
Message-ID: <C2D1868C-320A-4A59-B944-FA79576C112A@getmailspring.com> (raw)

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!), 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. 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?

Cole

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

             reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 16:04 Cole Poirier [this message]
2020-03-25 16:18 ` Luke Kenneth Casson Leighton
2020-03-25 16:22   ` Cole Poirier
2020-03-26  4:14     ` Luke Kenneth Casson Leighton
2020-03-26 19:42       ` Cole Poirier
2020-03-26 21:25         ` [libre-riscv-dev] email etiquette Jacob Lifshay
2020-03-26 21:33           ` Cole Poirier
2020-03-26 21:41           ` Luke Kenneth Casson Leighton
2020-03-26 22:41             ` Hendrik Boom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C2D1868C-320A-4A59-B944-FA79576C112A@getmailspring.com \
    --to=colepoirier@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git