New issue
Advanced search Search tips

Issue 714080 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

factory toolkit: par as installer.

Project Member Reported by hungte@chromium.org, Apr 21 2017

Issue description

Currently we have install_factory_toolkit.run and that contains factory.par. Also a factory-mini.par in test images.

However, Python can find dependent packages from zip files (without having that extracted to some where) - this is how our PAR was done.

This results an interesting question - do we really need factory.par inside installer?

If we can deprecate the makeself and replace with a python file and change format to zip, maybe we can make factory.par = install.run so we won't have to worry about repacking. Just one single PAR.

  factory.par gooftool # run as gooftool
  factory.par install # run the toolkit installer and unzip to somewhere


One thing to address is that Python does not support symlink when loading python modules files in ZIP file. But I think there are ways to solve, for example to de-reference when packing.
 

Comment 1 by hungte@chromium.org, Apr 21 2017

Summary: factory toolkit: par as installer. (was: toolkit: par = installer)

Comment 2 by hungte@chromium.org, May 18 2017

Cc: petershih@chromium.org

Comment 3 by hungte@chromium.org, Jul 14 2017

Cc: -youcheng@chromium.org -petershih@chromium.org -phoenixshen@chromium.org -stimim@chromium.org -littlecvr@chromium.org chromeos-factory-eng@google.com
Labels: Hotlist-GoodFirstBug
Owner: fshao@chromium.org
Status: Assigned (was: Untriaged)
Owner: jamesqaq@chromium.org

Sign in to add a comment