Archives
Archives
| From: | Alexis Ballier <aballier@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] Re: [RFC] TeX font cache, how to handle it, how to not (aka /var/cache/fonts sandbox violations) | ||
| Date: | Mon, 12 Nov 2007 19:11:54 | ||
| Message-Id: | 20071112200938.20ae3a4a@toz.strangled.net | ||
| In Reply to: | [gentoo-dev] Re: [RFC] TeX font cache, how to handle it, how to not (aka /var/cache/fonts sandbox violations) by Christian Faulhammer |
||
| 1 | On Mon, 12 Nov 2007 12:57:06 +0100 |
| 2 | Christian Faulhammer <opfer@g.o> wrote: |
| 3 | |
| 4 | > Alexis Ballier <aballier@g.o>: |
| 5 | > |
| 6 | > > Is it possible/wanted to do that automagically for every ebuild ? |
| 7 | > > Like adding it to portage env variables. Or should it be done in |
| 8 | > > each ebuild that needs it ? |
| 9 | > |
| 10 | > Those ebuilds surely inherit a TeX/LaTeX related eclass, maybe add it |
| 11 | > there. |
| 12 | |
| 13 | I don't think every such ebuild inherits such an eclass. Most of them |
| 14 | just call latex to generate some documentation. |
| 15 | |
| 16 | |
| 17 | Alexis. |
| File name | MIME type |
|---|---|
| signature.asc | application/pgp-signature |