Theoretically it would seem, if the emerge binaries were built and hosted along with what's out there now, dev_install could be used to emerge *NIX userland binaries generally, not just the current handful of binaries that are primarily for Chrome OS dev/debugging. There could be compilers, etc..
Could community members contribute such dev_install emerge binaries (not sure how those binaries get out there now), and if so, would they be accepted/hosted?
I presume that the use cases this question presupposes departs from the original use cases for dev_install, and the implications of what I'm asking are probably clear, but to be clear: perhaps if this were allowed/possible, Chrome OS would develop it's own add-on Linux "distribution", installed per individual taste via dev_install. Buy something off-the-shelf and keep the base OS with its verified boot security and auto updates from a well funded mother ship (Google), and add your own additional Linux userland as desired. The former makes this unlike building and maintaining Chromium OS on generic hardware or installing a HEX build, etc., and the later makes this very unlike the way the average person who buys a Google Chrome OS device would be using it.
Could community members contribute such dev_install emerge binaries (not sure how those binaries get out there now), and if so, would they be accepted/hosted?yes & no[hard] no: we aren't going to accept random .tbz2 packages from people.yes: submit an ebuild (ideally pulled from upstream Gentoo) to the portage-stable overlay, then add it to the chromeos-dev package.maybe: depending on the request, i'm not sure chromeos-dev will scale as we want because that controls all packages that go into a "dev" image. we might have to introduce a chromeos-dev-install package which our builders would use to seed the dev-installer repo.maybe (part 2): crap ebuilds are crap ebuilds and we don't want to support those :).
I presume that the use cases this question presupposes departs from the original use cases for dev_install, and the implications of what I'm asking are probably clear, but to be clear: perhaps if this were allowed/possible, Chrome OS would develop it's own add-on Linux "distribution", installed per individual taste via dev_install. Buy something off-the-shelf and keep the base OS with its verified boot security and auto updates from a well funded mother ship (Google), and add your own additional Linux userland as desired. The former makes this unlike building and maintaining Chromium OS on generic hardware or installing a HEX build, etc., and the later makes this very unlike the way the average person who buys a Google Chrome OS device would be using it.
we'd like to have a script that we ship that allows for easily managing secondary distros. unfortunately, we haven't had anyone step up just yet to implement this :). note: i'm not talking about scripts tailored for specific distributions -- we want a framework so that any random distro lover out there can add their own in w/out having to duplicate all the CrOS-specific pieces.
As another idea, developers could just host their own binhost.