From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Building Docker Containers
Date: Sun, 29 Mar 2020 16:14:56 +0000
Message-ID: <CAPweEDzWsAHJae6gz0rOV5vbUiU83SmkwOf-DyuqZ=xVteJxAA@mail.gmail.com> (raw)
In-Reply-To: <F07E7FAF-3BA5-4DE2-B2A4-99DA65503C4E@gatech.edu>
On Sun, Mar 29, 2020 at 5:03 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> Haha - well Georgia Tech where I am is more or less like an ISP so I have Gigabit internet when on campus - so no problems here.
yehyeh. this is normal. then we get someone like myself: in the
process of developing this project, just in the past two years i've
been to India, China, Taiwan, Okinawa Japan, Thailand, Hong Kong,
Spain, Belgium, Holland, England, Scotland, Canada, the U.S (briefly),
and so use
> I haven’t used chroot in years so I can look into that -
https://libre-riscv.org/HDL_workflow/coriolis2/
schroot. cole's looking at scripting that page (it's a matter of just
cut/pasting those commands) because it's needed for the build/test
server. do kick his tyres (yes, you cole :) ) and encourage him to
"release early, release often". as in, "i'll wait until it's perfect
and completed" *actively* prevents and prohibits collaboration. so if
you've got something, check it in *immediately*, ok?
(the OpenSourceEcology project actually have a rule that if you wait
more than 60 seconds before committing a file into an online
repository, that's a major red flag / violation of the collaborative
development rules)
> I’ve just always had a good experience with containers for snapshots.
snapshots. the key word there is: snapshots. as in, "something that
is expected to be thrown away rather than upgraded". as in, a
*multi-gigabyte download*.... each time.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 13:48 Immanuel, Yehowshua U
2020-03-29 15:26 ` Luke Kenneth Casson Leighton
2020-03-29 16:03 ` Immanuel, Yehowshua U
2020-03-29 16:14 ` Luke Kenneth Casson Leighton [this message]
2020-03-29 16:19 ` Immanuel, Yehowshua U
2020-03-29 16:24 ` Luke Kenneth Casson Leighton
2020-03-29 17:21 ` Jacob Lifshay
2020-03-29 18:48 ` Luke Kenneth Casson Leighton
2020-03-29 18:59 ` Jacob Lifshay
2020-03-29 19:33 ` Immanuel, Yehowshua U
2020-03-29 19:56 ` Jacob Lifshay
2020-03-29 19:57 ` Luke Kenneth Casson Leighton
2020-03-29 20:02 ` Jacob Lifshay
2020-03-29 20:51 ` Cole Poirier
2020-03-29 21:12 ` Luke Kenneth Casson Leighton
2020-03-29 21:34 ` Cole Poirier
2020-03-30 8:59 ` Luke Kenneth Casson Leighton
2020-03-30 18:13 ` Jacob Lifshay
2020-03-30 18:43 ` Cole Poirier
2020-03-30 18:58 ` Luke Kenneth Casson Leighton
2020-03-30 19:08 ` Jacob Lifshay
2020-03-30 19:31 ` Cole Poirier
2020-03-29 16:19 ` Luke Kenneth Casson Leighton
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='CAPweEDzWsAHJae6gz0rOV5vbUiU83SmkwOf-DyuqZ=xVteJxAA@mail.gmail.com' \
--to=lkcl@lkcl.net \
--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