app-text/texlive does provide virtual/tetex, but app-text/texlive-core does not. Installing texlive by emerging texlive-core, and additional dev-texlive/packages by hand, so to speak, means that virtual/tetex is left unsatisfied -- even though all that is needed, really, is installed. Reproducible: Always Steps to Reproduce: 0. (unmerge all tetex-stuff if installed) 1. Install app-text/tetexlive-core (and other stuff as you see fit form dev-texlive/) Actual Results: virtual/tetex is unsatisfied. Expected Results: virtual/tetex should be as content with dev-text/texlive-core as it would be with dev-text/texlive -- or, alternatively, with some (additional) package(s) from dev-texlive/. I have a functioning texlive system -- virtual/tetex should be satisfied. Perhaps the way to go should have been to emerge dev-text/texlive instead of texlive-core, sure, but I have it installed and everything works nicely. virtual/tetex *is* satisfied, in practice, with what I've emerged -- at least as far as I can tell. So even though this might not have been best practice, it works. Adding virtual/tetex to PROVIDED in dev-text/texlive-core would fix this for me.
As noted, you need dev-text/texlive and not dev-text/texlive-core. virtual/tetex is for the whole thing only, there's new-style virtual/latex-base and virtual/tex-base for what you want but that's something different... There's absolutely no way to group ebuilds to provide an old-style virtual.
yeah the point of having -core not providing virtual/tetex is that it provides much less packages than tetex. Now the goal is more or less to slowly kill virtual/tetex to use latex-base, tex-base & friends. If texlive-core provided virtual/tetex that would break deps for ebuilds that assume virtual/tetex means a working latex compiler with a few packages as texlive-core does not provide a latex compiler nor the latex packages. Anyway, if you notice ebuilds that depend on virtual/tetex, I'll be very thankful if you could report bugs & improved deps with latex-base or tex-base.
*** Bug 211943 has been marked as a duplicate of this bug. ***
Sorry for the duplicate, but i searched, and didn't find this bug.
