public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@gentoo.org>
To: Jason Cooper <gentoo@lakedaemon.net>
Cc: Sven Vermeulen <swift@gentoo.org>, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: Social Contract change & What is "Gentoo" ?
Date: Tue, 24 Aug 2004 12:32:14 -0400	[thread overview]
Message-ID: <412B6D8E.9070707@gentoo.org> (raw)
In-Reply-To: <20040824162348.GH18749@lakedaemon.net>

Jason Cooper wrote:

>Sven Vermeulen (swift@gentoo.org) scribbled:
>  
>
>>When you take a look at our current social contract
>>(http://www.gentoo.org/main/en/contract.xml) you will read that it talks
>>about "Gentoo Linux" exclusively. However, with Gentoo growing and non-Linux
>>ports in the make, it might be wise to change the naming from "Gentoo Linux"
>>to "Gentoo".
>>
>>The main question however is: "What is Gentoo"? When will we talk about
>>"Gentoo" and when do we talk about "a project" that "the Gentoo Project" is
>>working on?
>>
>>Based on the feedback I gathered from the managers meeting and from
>>developers, I'd like to propose something along the following lines:
>>
>>"""
>>We call a collection of software "Gentoo" when:
>>- it in total is able to boot itself (self-hosting)
>>- it is actively developed by the Gentoo Project
>>- its main software management application is a native Portage
>>    
>>
>
>What about an embedded system whose image was created using embedded
>gentoo tools, but contains no package management?  Or a minimal package
>management system (ipkg/apkg)?  Would that fall under "Embedded Gentoo" 
>or "Gentoo" or some customized thing?
>
>  
>
This is tricky but consider, Gentoo is a metadistribution meaning it's a 
"distribution of distributions", any distribution built with Gentoo is 
itself also Gentoo. An embedded system built from scratch using portage 
(even if not on the same system/arch) is Gentoo, even if the resulting 
system doesn't need/use portage..

On the other side, using portage as a complimentary package manager to 
build non-system applications (such as on OSX, Solaris, IRIX, etc) is 
not Gentoo because the system wasn't resultant from a Gentoo installation.

It works,  embedded is Gentoo but Portage on non-self-hosted OS's isn't, 
as my 'definitions' are no doubt very confusing I'd like to stick with 
what Swift has put.

Joshua Brindle

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-08-24 16:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 14:11 [gentoo-dev] Proposal: Social Contract change & What is "Gentoo" ? Sven Vermeulen
2004-08-24 16:23 ` Jason Cooper
2004-08-24 16:32   ` Joshua Brindle [this message]
2004-08-24 16:48 ` Pieter Van den Abeele
2004-08-24 21:30   ` Paul de Vrieze
2004-09-01  7:32     ` Sven Vermeulen
2004-09-01  7:55       ` Donnie Berkholz
2004-09-01  8:34       ` [gentoo-dev] " Duncan
2004-09-01 11:31         ` Paul de Vrieze
2004-09-01 14:20           ` [gentoo-dev] " Duncan
2004-09-09 12:25             ` Sven Vermeulen
2004-09-10 17:35               ` [gentoo-dev] " Duncan
2004-09-11 11:36                 ` Sven Vermeulen
2004-09-13 15:37                   ` [gentoo-dev] " Duncan
2004-09-14  1:35                     ` Allen Parker
2004-09-14 11:40                     ` Sven Vermeulen
2004-09-14 12:13                       ` Sven Vermeulen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=412B6D8E.9070707@gentoo.org \
    --to=method@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo@lakedaemon.net \
    --cc=swift@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox