| 1 |
On 09/25/2011 06:57 PM, Nirbheek Chauhan wrote: |
| 2 |
> On Mon, Sep 26, 2011 at 7:02 AM, Mike Frysinger <vapier@g.o> wrote: |
| 3 |
>> On Sunday, September 25, 2011 05:53:18 Nirbheek Chauhan wrote: |
| 4 |
>>> "Gentoo" is defined by portage and the portage tree. If we remove |
| 5 |
>>> that, the end result is no different than compiling stuff manually in |
| 6 |
>>> Slackware or by hand. |
| 7 |
|
| 8 |
Sure, the average Chrome OS end user may not know the difference. |
| 9 |
However, it makes a difference to the Gentoo community to have our tools |
| 10 |
and tree used by Chrome OS developers, and have them contribute back |
| 11 |
fixes and enhancements. |
| 12 |
|
| 13 |
>> which is how Chrome OS is built. |
| 14 |
>> ROOT=/some/place emerge <some binpkgs> |
| 15 |
>> |
| 16 |
> |
| 17 |
> Yes, I'm well aware of how ChromeOS is built. :) |
| 18 |
> |
| 19 |
> But neither portage, nor the portage tree, nor any of our branding are |
| 20 |
> shipped with ChromeOS. Hence it's as much a Gentoo install as $company |
| 21 |
> that uses portage to build $image for their embedded device, but |
| 22 |
> doesn't leave any trace of Gentoo behind. |
| 23 |
|
| 24 |
So what? I work on Gentoo for the benefit of myself and others |
| 25 |
(including Chrome OS devs), not because I want people to see Gentoo |
| 26 |
branding, or have more people identify themselves as "Gentoo users." |
| 27 |
-- |
| 28 |
Thanks, |
| 29 |
Zac |
Archives