Graphyte: Setup manifest and ebuild |
||||
Issue descriptionGraphyte became a public repo. We need to add it into manifest and setup a ebuild for it.
,
Dec 9 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/manifest-internal/+/ff0c4f1ff26fd08e682e85cbcb9b8ad654657795 commit ff0c4f1ff26fd08e682e85cbcb9b8ad654657795 Author: Chih-Yu Huang <akahuang@google.com> Date: Mon Dec 05 03:19:59 2016
,
Jan 17 2017
Also need to add LitePoint partner repo into private manifest, which is the only standalone private repo.
,
Jan 17 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/manifest-internal/+/eecb364d1cdee0bf6c070bd1956a927615f7982c commit eecb364d1cdee0bf6c070bd1956a927615f7982c Author: Chih-Yu Huang <akahuang@google.com> Date: Tue Jan 17 08:02:09 2017
,
Jul 26 2017
Do we have anything left here to do?
,
Jul 26 2017
The ebuild of Graphyte framework is ready, but the one of Litepoint private repo hasn't finished. However, we don't use emerge to build, install, or deploy Graphyte framework. I think actually we don't need to write ebuild... Set to won't fix now. If we want to integrate Graphyte package into factory toolkit in the future, then we can open it again. |
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Dec 6 2016