Re: texlive & evince

Hi,

On Fri, Feb 01, 2019 at 10:49:56PM +0000, Edd Barrett wrote:
> On Thu, Jan 24, 2019 at 10:07:15AM +0000, Edd Barrett wrote:
> > I agree that it's not good for users to have to install a texmf subset
> > just to use evince. I'm OK with evince lib depending upon texlive-base
> > in the interim until we decide what to do, but in the long term we don't
> > want that heavy dependency.
>
> So, unless I am mistaken, our evince package works because it either
> picks up synctex from texlive_base if it's installed by chance at pkg
> time, or else it is using its internal copy of synctex.

Yes, that's bad. Please note that evince has a 'light' FLAVOR. which may
make things even more complicated.

> What do we want to do?
>
> - In tex live, put synctex into its own subpackage and LIB_DEPEND it.
> - In tex live, move synctex into -mktexlsr. Evince already LIB_DEPENDS this.
> - Patch evince to always use its internal copy.
>
> FWIW, I'm leaning towards the first option.

First or third. The second option just sounds wrong -- mktexlsr is
meant to only include, well, mktexlsr and the kpathsea bits, isn't
it?.

Has anyone build logs of evince,light around? Does it check for
synctex, and build differently wether it's already installed or
not?

Ciao,
Kili