From: Blake Matheny <jake@gentoo.org>
To: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Portage Category: dev-scheme
Date: Mon, 26 Jan 2004 22:26:53 -0500 [thread overview]
Message-ID: <20040127032653.GB19441@dev.gentoo.org> (raw)
In-Reply-To: <20040126201931.339e5119@wallace.fasmz.org>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Whatchu talkin' 'bout, Willis?
> What about a dev-commonlisp category then? Like there is app-emacs
> (resp. app-vim) for emacs (resp. vim) packages, whereas other editors
> goes to app-editors.
Unfortunately I think the most correct solution isn't one that's available.
What would be correct, is having dev-scheme and dev-cl categories as sub
categories of dev-lisp, since technically Scheme and CL are both dialects of
Lisp. However this isn't an option. Creating dev-commonlisp is no better of a
solution than creating dev-scheme imho.
-Blake
--
Blake Matheny
jake@gentoo.org Computer Science is merely the post-Turing
http://dev.gentoo.org/~jake/ decline in formal systems theory.
http://mkfifo.net/gpg.key
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-27 3:10 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 [this message]
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
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=20040127032653.GB19441@dev.gentoo.org \
--to=jake@gentoo.org \
--cc=degrenier@easyconnect.fr \
--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