[Libre-soc-bugs] [Bug 714] Coriolis2 Installation as Normal User Script

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Thu Oct 7 12:50:08 BST 2021


--- Comment #24 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to andrey from comment #23)
> I've made a top-level script that sets up the chroot and Coriolis2 (as
> outlined in comment #1). Ran it once (after making sure "coriolis-install"
> already worked), and it works (from creating chroot all the way to
> displaying the chip_r floorplan)!

hooraaay :)

> The default chroot name I'm using is "coriolis". Should I change this, or
> perhaps provide an optional input argument?

ah yes that's a good idea

> The script also checks if a chroot exists, and if it does, exits before
> doing anything. This is because I don't expect a user to be re-running the
> script more than once.
> Once the chroot is setup, "coriolis-install" can be run independently.

good idea

> The wiki pages for Coriolis2 and devscripts have been updated (I moved the
> chroot information there as it is applicable to other software).

i saw that.  nice touch about referring to documentation in the script.
i'm glad you kept the original "manual" instructions, it helps for
people who want to know what is going on.

>  Have a go
> running the script "coriolis2-chroot" if you have time (probably before
> going off for lunch or something).

well, i already have a chroot named coriolis (and use it) so that would
clearly be bad :) and would justify the extra argument.

> Also after checking the color codes used in mk-deb-chroot, I found a
> convenient way to change echo text colour:
> RED='\033[1;91m'
> NC='\033[0m'
> echo -e "${RED}This text is in red,${NC} while this text is plain (no
> colour)."


You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-soc-bugs mailing list