From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14158 invoked from network); 27 Jan 2004 18:58:03 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 27 Jan 2004 18:58:03 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1AlYPT-0007Wk-4x for arch-gentoo-dev@lists.gentoo.org; Tue, 27 Jan 2004 18:58:03 +0000 Received: (qmail 11626 invoked by uid 50004); 27 Jan 2004 18:57:03 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 16613 invoked from network); 27 Jan 2004 18:57:03 +0000 To: gentoo-dev@lists.gentoo.org References: <20040124215745.GA4315@dev.gentoo.org> <1075108037.13477.11.camel@green> <20040126172638.GA19441@dev.gentoo.org> <20040126173655.484C29443A@mail.lasierra.edu> <87ptd61qcq.fsf@killr.ath.cx> <20040127034902.GA13365@phaenix.haell.com> From: Matthew Kennedy Date: Tue, 27 Jan 2004 12:56:05 -0600 In-Reply-To: <20040127034902.GA13365@phaenix.haell.com> (Drake Wyrm's message of "Mon, 26 Jan 2004 19:49:02 -0800") Message-ID: <87vfmxdxve.fsf@killr.ath.cx> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Subject: Re: [gentoo-dev] New Portage Category: dev-scheme X-Archives-Salt: 744df456-020c-4b35-8cef-e9bc62d309c2 X-Archives-Hash: 17c93d9501f30d9842078d8ab224b723 --=-=-= Content-Type: text/plain Drake Wyrm writes: [...] > describes its intended contents, I suggest "dev-lispscheme. One > alternative, just off the top of my head, would be to use "dev-scheme" > and drop a README in the Portage tree root directory which describes > what each category is supposed to contain and points to other detailed > documentation. Folks, you are making a meal out of this category naming!!! Haven't we got more pressing tasks at hand? dev-scheme and dev-lisp are good enough name spacing. Once the Scheme stuff is moved from dev-lisp to dev-scheme, all that remains in dev-lisp is approximately 100 Common Lisp-related ports and xlispstat and lush (which are not Scheme or Common Lisp, but have a S-expression syntax). At that point, we'll *maybe* create dev-common-lisp and leave xlispstat and lush in dev-lisp -- but I can't see justifying a category with only 2 ebuilds in it, so lush and xlispstat will have to move to dev-lang while dev-lisp would be dropped. It is my preference as a maintainer of dev-lisp to leave xlispstat, lush and all the Common Lisp stuff in dev-lisp and move the scheme stuff to dev-scheme. Matt -- Matthew Kennedy Gentoo Linux Developer --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAFrRhyiNZaEAZA+ARAq2+AKCDiUGHKYolwhm8vA0gZBeWx2gfPQCeIiEA rjW746nRoE8G368hIGRZZJU= =nrNV -----END PGP SIGNATURE----- --=-=-=--