| Summary: | tetex 3.0 doesn't include pgf 1.01 and blocks the separate ebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Gregor Riepl <seto-kun> |
| Component: | New packages | Assignee: | TeX project <tex> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | aballier, chithanh, michael.kiermaier, prote, tim |
| Priority: | High | ||
| Version: | 2006.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | pgf-1.09.ebuild | ||
|
Description
Gregor Riepl
2006-07-30 09:00:13 UTC
(In reply to comment #0) > for now, how about a temporary texmf patch and marking ptex 3 as a blocker for > pgf, xcolor and xkeyval? What kind of patch do you mean? And yeah, this is wrong place for this request, needs to go upstream... This bug will get fixed as soon as tetex-3 goes stable. The newest ~arch version does include a texmf-site texmf-tree where the latex-package should install all in-tree tex-packages so they do not conflict with the ones in the standard texmf-tree. with a temporary fix, i mean preparing a patch that removes pgf from the texmf tree and replaces it with the current 1.01 version. what exactly will get fixed in tetex 3 stable? your post is a bit too technical for me. :/ as far as i understood, the fix here will be providing a separate site-installation directory for additional packages so the ones from texmf won't get overwritten. is that correct? by the way, as things are now, ptex should really be included in the dev-tex/*'s package blockers, not only tetex. it uses texmf in the same way and has the same limitations. ok, this would be a different bug, but is it worth opening another report? maybe virtual/tetex should get a version and that be used in lieu of >=app-text/tetex-3.0. tetex-3.0_p1-r3 is presently being marked as stable in bug 154489. I needed to remove those packages : emerge -avC dev-tex/pgf dev-tex/xcolor dev-tex/latex-beamer dev-tex/xkeyval dev-tex/lineno prior to update world. (In reply to comment #3) > with a temporary fix, i mean preparing a patch that removes pgf from the texmf > tree and replaces it with the current 1.01 version. > > what exactly will get fixed in tetex 3 stable? your post is a bit too technical > for me. :/ > as far as i understood, the fix here will be providing a separate > site-installation directory for additional packages so the ones from texmf > won't get overwritten. is that correct? I encountered the same problem today after upgrading to tetex-3.0. Here is my interim solution until pgf-1.x becomes part of tetex: (I assume you have defined a portage overlay in /etc/make.conf, e.g.: PORTDIR_OVERLAY="/usr/local/portage") mkdir -p /usr/local/portage/dev-tex/pgf/files cd /usr/local/portage/dev-tex/pgf/ vi pgf-1.09.ebuild (contents see attachment) ebuild pgf-1.09.ebuild digest echo ">=dev-tex/pgf-1.09 ~x86" >> /etc/portage/packages.keywords emerge pgf This installs pgf-1.09 into the local TeX tree /usr/local/share/texmf that is searched before the distribution TeX tree /usr/share/texmf. Created attachment 102600 [details]
pgf-1.09.ebuild
I added a newer pgf-version to the portage tree which works in combination with tetex-3. It's currently ~arch, but please test. (In reply to comment #8) > ... but please test. Done. No problems (more precisely: the problems I had with older versions are solved). In fact we use pgf-1.18 (and latex-beamer-3.07) since July 4-th without any problems. I had my own ebuilds in a local overlay that look pretty much the same than yours. So I would vote for a quick stabilization of both, pgf-1.18 and latex-beamer-3.07 (see your bug 185096). |
