[libre-riscv-dev] Setup automation scripts

[libre-riscv-dev] Setup automation scripts

[Cole Poirier]

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

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

[Luke Kenneth Casson Leighton]

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


> 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.

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

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

[Cole Poirier]

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

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

[Luke Kenneth Casson Leighton]

cole click the three dots first before reading this further...

On Wednesday, March 25, 2020, Cole Poirier <colepoirier@gmail.com> wrote:

>
>
> 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.


... which includes trimming context on replies.  you see how much crap
there is, how long it took to scroll down and find this?

not everyone is using gmaul.

l.


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


-- 
---
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

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

[Cole Poirier]

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

> cole click the three dots first before reading this further...

> ... which includes trimming context on replies.  you see how much crap
> there is, how long it took to scroll down and find this?
> 
> not everyone is using gmaul.
> 
> l.

Sorry for this lapse in judgement Luke. I've been trying my best to
adhere to proper mailing list etiquette, and I've switched to using the
open source mail client Mailspring to allow me to make sure I'm sending
plaintext mail. But of course, this doesn't prevent me from slipping
into my old ways, so thank you for this reminder, I'll try very hard not
to do this again.

Cole

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

[libre-riscv-dev] email etiquette

[Jacob Lifshay]

On Thu, Mar 26, 2020, 12:43 Cole Poirier <colepoirier@gmail.com> wrote:

> Sorry for this lapse in judgement Luke. I've been trying my best to
> adhere to proper mailing list etiquette, and I've switched to using the
> open source mail client Mailspring to allow me to make sure I'm sending
> plaintext mail. But of course, this doesn't prevent me from slipping
> into my old ways, so thank you for this reminder, I'll try very hard not
> to do this again.
>

We're not like some of the Kernel mailing lists which will just block any
mail with html, so you can still use the gmail client if you want, just
remember to try to trim excessive context, avoid top-posting, and avoid
using non-plaintext features.

I'm currently writing this in the gmail app for android, in case you were
wondering.

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

Re: [libre-riscv-dev] email etiquette

[Cole Poirier]

> On Mar 26, 2020, at 2:25 PM, Jacob Lifshay <programmerjake@gmail.com> wrote:
> 
> We're not like some of the Kernel mailing lists which will just block any
> mail with html, so you can still use the gmail client if you want, just
> remember to try to trim excessive context, avoid top-posting, and avoid
> using non-plaintext features.
> 
> I'm currently writing this in the gmail app for android, in case you were
> wondering.
> 
> Jacob

Will do! Thanks for the advice Jacob!

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

Re: [libre-riscv-dev] email etiquette

[Luke Kenneth Casson Leighton]

On Thu, Mar 26, 2020 at 9:25 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Thu, Mar 26, 2020, 12:43 Cole Poirier <colepoirier@gmail.com> wrote:
>
> > Sorry for this lapse in judgement Luke. I've been trying my best to
> > adhere to proper mailing list etiquette, and I've switched to using the
> > open source mail client Mailspring to allow me to make sure I'm sending
> > plaintext mail. But of course, this doesn't prevent me from slipping
> > into my old ways, so thank you for this reminder, I'll try very hard not
> > to do this again.
> >
>
> We're not like some of the Kernel mailing lists which will just block any
> mail with html,

yeah that one's fun.  at least it warns you with a reject rather than
silent treatment.  the reason they only accept plaintext is because
the key kernel developers have mail-filters which look for
git-format-patch messages.  therefore you absolutely do not want
html-formatted crap.  plus, on (literally) the world's largest
software project (by a long, long margin) it just pisses a *lot* more
people off.

> so you can still use the gmail client if you want, just
> remember to try to trim excessive context, avoid top-posting, and avoid
> using non-plaintext features.
>
> I'm currently writing this in the gmail app for android, in case you were
> wondering.

i'm also on gmail "m.gmail.com" in a web browser with "mobile tab"
set.  sigh it defaults to html (with no option to set plaintext).
however - yes, i still always trim context.

it's just habit.

l.

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

Re: [libre-riscv-dev] email etiquette

[Hendrik Boom]

On Thu, Mar 26, 2020 at 09:41:13PM +0000, Luke Kenneth Casson Leighton wrote:
> On Thu, Mar 26, 2020 at 9:25 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> 
> 
> > so you can still use the gmail client if you want, just
> > remember to try to trim excessive context, avoid top-posting, and avoid
> > using non-plaintext features.
> >
> > I'm currently writing this in the gmail app for android, in case you were
> > wondering.
> 
> i'm also on gmail "m.gmail.com" in a web browser with "mobile tab"
> set.  sigh it defaults to html (with no option to set plaintext).
> however - yes, i still always trim context.

I've noticed an increasing number of people are sending me html only.
I think many of them don't know they're doing it, don't know what it
is, and don't know how to stop it.

SOmeone seems to be encouraging it by setting defaults in popular software.

-- hendrik

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