New issue
Advanced search Search tips

Issue 863612 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

git repo for chrootless commands

Project Member Reported by dnschn...@chromium.org, Jul 13

Issue description

I've been maintaining scripts that allow for chrootless usage of servod, dut-control, (Chromium OS's) flashrom, and the hdctools flash_ec script.  I posted an internal PSA [1].

Since we're open-sourcing stuff like case-closed debug [2], I believe it would make sense to make these scripts externally accessible as well; then the scripts could be used by anyone with just a git clone of a tiny repo, and we can update instructions with the much lighter chrootless variant.

Would this make sense?  Can we create a repo for it?
I was thinking of a location like chromium.googlesource.com/chromiumos/nochroot

[1] https://groups.google.com/a/google.com/forum/#!topic/chromeos-chatty-eng/U-cv7pxrHlk
[2] https://sites.google.com/a/chromium.org/dev/chromium-os/ccd
 
Cc: vapier@chromium.org
we generally avoid putting things directly under chromiumos/.  that isn't for generic projects.

if you want a repo under chromiumos/platform/, we're pretty easy going.

the name "nochroot" is kind of bad though :p.
Yeah, definitely not my most inspired naming.  Any suggestions?
"flash-helper-tools"
"simple-flash-helpers"
"standalone-flash-tools"
"external_tools" for a boring but somewhat descriptive name?
I like "standalone-tools"
Yeah, I'd be happy with chromium.googlesource.com/chromiumos/platform/standalone-tools

it's almost poetic
if your focus is on flash/ccd tools, seems like that should be in there.  you aren't creating standalone tooling for everything (e.g. building or anything related to CrOS userspace).
If the repo would end up being a place to add other commands that already exist w/in the cros sdk but unavailable from some other repo + pkg manager outside then I could see something a bit more generic

cros_sdk-standalone-tools
chromite-standalone-tools

Else keeping the focus narrower (prefix: flash, debug, hdc, ccd) as mentioned would be my choice too.


tools in chromite are already standalone (where makes sense).  i don't see the value in trying to replicate their usage and making them "simpler".

any attempt to simplify the build by creating standalone shell scripts that are external to chromite is a lost cause and doesn't really make sense.

i grok making it easier to use low level flash related tooling.
OK, how about standalone-hdctools?
any standalone-<some firmware package name or qualifier> sounds fine
Great, could someone please make that repo?
normal ACLs on this OK even though it's not going to be in the manifest ?  you'd have to manually git push to create gerrit reviews, but otherwise everything else would "just work".
Yep, that's fine.
Labels: -Restrict-View-Google
Owner: vapier@chromium.org
Status: Fixed (was: Untriaged)
should be all set now
  https://chromium.googlesource.com/chromiumos/platform/standalone-hdctools

Sign in to add a comment