From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new category for texlive modular ebuilds?
Date: Thu, 11 Oct 2007 22:00:38 -0700 [thread overview]
Message-ID: <20071012050038.GA14030@phaenix.haell.com> (raw)
In-Reply-To: <20071011195149.44c9f7de@toz.strangled.net>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Alexis Ballier <aballier@gentoo.org> wrote:
> Hi,
>
> this might be worth discussion also (and make me even more late on my
> schedule with merging texlive, but I knew I'd be)
>
> In my overlay I was using a dev-texlive category for the texlive
> modular texmf ebuilds
> [as a side note :
> dev-texlive $ ls | wc -l
> 79
> ]
>
> that was to avoid polluting dev-tex (which would be the current most
> suitable category for those ebuilds), but well, both categories are fine
> by me. What do you think about it ? I'd say not polluting it and put
> them in a new category is better as it doesn't cost anything, but I
> might have missed something.
I would have expected app-text, the current home of the other TeX
interpreters, to be more appropriate than dev-tex. Then again, with 79
new ebuilds, it might be prudent to open another category. If you did
that, though, I'd suggest putting texlive and the other TeX interpreters
in the same category. Perhaps app-tex would be good. Would that cause
much confusion, being one letter off from an existing category?
On the other hand (or is this back on the first hand?), 79 new packages
wouldn't be much of a splash in the 231 existing packages of app-text.
--
The only time I use xp is when I need to swap a pair of letters.
[-- Attachment #2: Type: application/pgp-signature, Size: 206 bytes --]
next prev parent reply other threads:[~2007-10-12 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 17:51 [gentoo-dev] new category for texlive modular ebuilds? Alexis Ballier
2007-10-12 5:00 ` Drake Wyrm [this message]
2007-10-12 7:47 ` Alexis Ballier
2007-10-13 13:40 ` Alexis Ballier
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=20071012050038.GA14030@phaenix.haell.com \
--to=wyrm@haell.com \
--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