[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-users
Subject:    Re: texlive no longer finds (some of) its style files?
From:       Mojca Miklavec <mojca () macports ! org>
Date:       2019-07-08 12:45:56
Message-ID: CALBOmsZmGxc0CohS0pYcN2Lv9XkdBt4YxEdXotEE-TyTsknazQ () mail ! gmail ! com
[Download RAW message or body]

On Mon, 8 Jul 2019 at 14:27, Ryan Schmidt wrote:
>
> I don't think MacPorts will uninstall a port unless you tell it to (direc=
tly by name@version_revision+variants, or using a pseudoport (like "inactiv=
e" or "leaves"), or using port(1)'s "-u" flag).
>
> What could happen, though, is that MacPorts might deactivate a port if an=
other port has replaced its functionality. For example, if a port texlive-o=
ld no longer exists but a port texlive-new now provides the same files that=
 texlive-old used to, then when you install or upgrade texlive-new, it will=
 automatically deactivate texlive-old. The result should be that the files =
you want are still there. If somehow that didn't end up being the case, you=
 could reactivate texlive-old.
>
> If you selectively update ports, you can run into situations where some o=
f a port's dependencies have been updated but others haven't. This can resu=
lt in a variety of problems, possibly including the one you mentioned. For =
this reason, we recommend using "sudo port upgrade outdated" to upgrade all=
 of the outdated ports at once, and not selectively upgrading ports.

With TeX Live one can definitely run into situations of a package
being in one collection, then moved to another collection next year.
And your document suddenly no longer compiles despite having the same
packages installed (but now some files missing), and the only safe way
around it is to install the full texlive.

Mojca
[prev in list] [next in list] [prev in thread] [next in thread]