Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 196246
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: TeX herd <tex@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Alexis Ballier <aballier@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 196246 depends on: Show dependency tree
Bug 196246 blocks: 195815
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-10-18 07:34 0000
tetex and the current texlive ebuilds use texlinks for creating symlinks from
formats to engines, like latex -> pdftex in /usr/bin for texlive.

The problem of handling files via texlinks is that those files are not under
the control of portage, thus unmerging tetex or texlive leaves the symlinks
around, pointing to nothing.
I'm almost finished writing/importing the functions of texlinks in the eclass
and creating the symlinks there, so that they will be in CONTENTS.

The drawback of doing this is that if somebody had a previously installed
version, that will cause collisions with those files that are on the system and
don't belong to any package.

As migrating to texlive will be a big step, I think it's the right time to fix
that.

------- Comment #1 From Alexis Ballier 2007-10-21 11:32:09 0000 -------
this is now fixed by using etexlinks from texlive-common.eclass

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug