On Mar 19, 2025, at 7:11 AM, Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote:
Hello,
In the Message;
Subject : Re: how can I find a package responsible for drawing in texlife (very stubbornly) Message-ID : <99A9993E-DACF-4455-B670-50E8D1B46E3F@tabris.net> Date & Time: Wed, 19 Mar 2025 06:20:50 -0400
[T] == tabris@tabris.net has written:
AB> > Yes, that automates getting the list of what packages provide. You AB> > still need to run it for every of the 9095 packages, but it is trivial AB> > shell programming (assuming the list of these packages is available).
T> You could run it for all 9095... but chances are you only need at T> most a dozen... albeit you may not know which is the topmost in T> the hierarchy. T> But you can also take a good guess, because most likely there's T> just one package that pulls in the other 9000 or so. And it's T> probably a short name.
Because the TeX Live packages depend on many other packages, this can cause complications in the dependency structure. In particular, because each component of TeX Live depends on different libraries and tools, if these dependencies are broken, it can affect the entire system.
So it is better to ask YaST2 to remove it.
I think you understood a different question than I did: which package[s] is pulling in texlive? Yes, use the most capable tool for the removal of your packages. I just meant that the search itself wasn't likely to require the toil that 9000 packages might imply. Also the original post suggested he had already blacklisted them, but he didn't want to do so going forward. He wanted to find the cause of the ostensibly extraneous dependencies, and blacklist the culprits.