From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: *** X-Spam-Status: No, score=3.1 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DMARC_REJECT,FORGED_YAHOO_RCVD,FREEMAIL_FROM,MAILING_LIST_MULTI, RDNS_NONE,SPOOFED_FREEMAIL_NO_RDNS autolearn=no autolearn_force=no version=4.0.0 Received: from uranus.u235.eyep.net (unknown [194.90.113.98]) by chiba.3jane.net (Postfix) with SMTP id E6F53200B29D for ; Mon, 4 Feb 2002 05:44:36 -0600 (CST) Received: (qmail 14294 invoked by uid 1000); 4 Feb 2002 11:43:41 -0000 Subject: Re: [gentoo-dev] A new category scheme idea From: Vitaly Kushneriuk To: Gentoo-dev In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 04 Feb 2002 13:43:40 +0200 Message-Id: <1012823020.10863.14.camel@uranus.u235.eyep.net> Mime-Version: 1.0 Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: f500b2d6-3be8-4cdd-b612-bcb3bc968097 X-Archives-Hash: 64dcc7d093765e80a689ce5c8c945bec On Mon, 2002-02-04 at 13:25, gentoo-user@devrieze.net wrote: > On Mon, 4 Feb 2002, Einar Karttunen wrote: > > > Hello > > > > I have thought about a new way of categorise ebuilds in gentoo. The > > new scheme would be based on category files which would be just a > > list of dependencys as portage understands them. Each package could > > be in many categories and categories may include categories (but there > > may be no circular references). > > > > I agree on your point that category files are usefull. You certainly have > a point. I don't think though the categories in the portage tree should > vanish. I prefer to see category files as an addition to the "main > category" of each package. The reason I want that is that I think the > system would become unmanageable if the packages are uncategorized. There > are just too many packages, if you want to put them all in one directory, > it will be hell to find them or maintain them. Next the categorizing > allows for duplicate names. Finally I think category files with qualified > packages are not harder to make than category files without qualified > packages. Unqualifying packages is a considerable job though, so I prefer > to give each package a "main" category, and use category files for > aditional categories. Just an idea: to simplify it we can have *optional* KEYWORDS="xxx yyy" in ebuild file, and "emerge --update-keywords" command to scan through available ebuilds and dump their names to apropriate files under /usr/portage/keywords i.e. if in dev-lang/python-2.1.1-r3.ebuild, there's KEYWORD="DEVELOPMENT PYTHON COMPILER" dev-lang/python-2.1.1-r3 will be appended to /usr/portage/keywords/{DEVELOPMENT,PYTHON,COMPILER} /Vitaly