From: Matthew Kennedy <mkennedy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Portage Category: dev-scheme
Date: Tue, 27 Jan 2004 12:56:05 -0600 [thread overview]
Message-ID: <87vfmxdxve.fsf@killr.ath.cx> (raw)
In-Reply-To: <20040127034902.GA13365@phaenix.haell.com> (Drake Wyrm's message of "Mon, 26 Jan 2004 19:49:02 -0800")
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Drake Wyrm <wyrm@haell.com> 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
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2004-01-27 18:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 21:57 [gentoo-dev] New Portage Category: dev-scheme Blake Matheny
2004-01-24 22:54 ` Matthew Kennedy
2004-01-26 9:07 ` Grant Goodyear
2004-01-26 17:26 ` Blake Matheny
2004-01-26 18:05 ` Brian Friday
2004-01-26 19:07 ` Matthew Kennedy
2004-01-26 19:19 ` Thomas de Grenier de Latour
2004-01-27 3:26 ` Blake Matheny
2004-01-27 3:49 ` Drake Wyrm
2004-01-27 5:08 ` Seemant Kulleen
2004-01-27 5:37 ` Blake Matheny
2004-01-27 6:47 ` Olivier Crête
2004-01-27 8:02 ` Blake Matheny
2004-01-27 9:14 ` Drake Wyrm
2004-01-27 12:16 ` Chris Gianelloni
2004-01-27 13:29 ` Jean Jordaan
2004-01-27 18:25 ` George Shapovalov
2004-01-27 18:34 ` Matthew Kennedy
2004-01-27 18:56 ` Matthew Kennedy [this message]
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=87vfmxdxve.fsf@killr.ath.cx \
--to=mkennedy@gentoo.org \
--cc=gentoo-dev@lists.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