Alexis Ballier <[EMAIL PROTECTED]> 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.
pgp6qfk2jmIHn.pgp
Description: PGP signature
