| 1 |
Hi, |
| 2 |
|
| 3 |
> There are two methods commonly used to fight against this situation |
| 4 |
> in ebuilds: using addwrite or setting VARTEXFONTS="${T}/fonts". The |
| 5 |
> second method is, probably, better. |
| 6 |
|
| 7 |
Packages should definitely go for the VARTEXFONTS one as I'll probably |
| 8 |
drop forced global writable /var/cache/fonts at some point in the |
| 9 |
texmf-update script (not that its a security issue but I really dont |
| 10 |
like having it like that); if its not world writable and a package |
| 11 |
needs to build some fonts and isn't run as root (default nowadays?) the |
| 12 |
addwrite will not allow it to write there afaik and it will fail. |
| 13 |
Nice you have such a list, please assign a bug to tex@g.o for that and |
| 14 |
I'll see what I can do to convert them (perhaps adding the maintainers |
| 15 |
in case they want to know what's up and are willing to help). |
| 16 |
See: |
| 17 |
https://bugs.gentoo.org/show_bug.cgi?id=204433 |
| 18 |
http://groups.google.com/group/linux.gentoo.dev/browse_thread/thread/bf2e58fe200c0676/b72be3596cd2eb31 |
| 19 |
|
| 20 |
|
| 21 |
> Most disturbingly, there are a number of packages which (probably) |
| 22 |
> run latex and do neither addwrite nor VARTEXFONTS. An incomplete list |
| 23 |
> of such suspect packages is (for now, I only considered packages not |
| 24 |
> directly related to TeX/LaTeX, i.e., not in dev-tex or dev-texlive |
| 25 |
> and not TeX/LaTeX packages in app-text): |
| 26 |
[...] |
| 27 |
> These are (potentially) bombs waiting to blow up an unsuspecting |
| 28 |
> user. They should be carefully checked. |
| 29 |
|
| 30 |
Yeah or maybe they dont need any unusual fonts; its probably sane to |
| 31 |
set VARTEXFONTS regardless. Probably it'd be worth adding a latex |
| 32 |
eclass that would just contain: |
| 33 |
VARTEXFONTS=${T}/fonts |
| 34 |
and inherit it from any package calling latex to avoid code duplication |
| 35 |
(like e.g. the mono eclass do). |
| 36 |
What do you think ? |
| 37 |
|
| 38 |
|
| 39 |
> By the way, while investigating this question, I found quite a few |
| 40 |
> packages which still depend on virtual/tetex, while, probably, |
| 41 |
> virtual/latex-base would be better |
| 42 |
|
| 43 |
Yep, it would be cool to kill virtual/tetex because it does not make |
| 44 |
much sense nowadays. Some might be false positives but please also file |
| 45 |
a bug for tex@g.o with that list and cc the maintainers to see what can |
| 46 |
be done. |
| 47 |
|
| 48 |
|
| 49 |
Regards, |
| 50 |
|
| 51 |
Alexis. |
Archives