I'm working on updating FreeCAD both for Python 3.9 and coming VTK 9.0 and I noticed that something is pulling in a lot of texlive packages but I am not BR'ing any. First, how do I figure out which package is doing it? There's not enough info in root.log AFAIKT. Second, once I find the package, how to determine if it really needs texlive? Thanks, Richard

I'm working on updating FreeCAD both for Python 3.9 and coming VTK 9.0 and I noticed that something is pulling in a lot of texlive packages but I am not BR'ing any.

On Sat, May 30, 2020 at 10:31 AM Zbigniew Jędrzejewski-Szmek < zbyszek(a)in.waw.pl&gt; wrote: > On Sat, May 30, 2020 at 10:01:50AM -0500, Richard Shaw wrote: > > I'm working on updating FreeCAD both for Python 3.9 and coming VTK 9.0 > and > > I noticed that something is pulling in a lot of texlive packages but I am > > not BR'ing any. > > I'm seeing this too, with ~100 texlive packages pulled in on upgrade > in a VM. I think this is caused by new dependencies between texlive > package. E.g. I had texlive-kpathsea installed, presumably because it > is required by texlive-dvipng which is required by python3-matplotlib, > and upon upgrade this pulls in texlive-context, which pulls in > texlive-pstricks, which pulls in texlive-biblatex, which pulls in > texlive-xpatch, and so on. The dep was added back in #1270202. > > Dunno. python3-matplotlib pulling in the whole latex stack is going to > be painful. Maybe we could "downgrade" the dependency in python-matplotlib > to something like > Recommends: dvipng > Requires: (dvipng if texlive-base) > ? > That's actually it! I think moving it to Recommends (if it doesn't break anything) would be a good idea. I assume Recommends are not installed in koji/mock?