Hi, On Thu, Feb 07, 2019 at 05:34:35PM +0100, Jeremie Courreges-Anglas wrote: > > Index: pkg/PLIST-synctex > > =================================================================== > > RCS file: pkg/PLIST-synctex > > diff -N pkg/PLIST-synctex > > --- /dev/null 1 Jan 1970 00:00:00 -0000 > > +++ pkg/PLIST-synctex 4 Feb 2019 17:39:55 -0000 > > @@ -0,0 +1,15 @@ > > +@comment $OpenBSD$ > > +@conflict teTeX_base-* > > +@conflict pdfjam-* > > +@conflict ht-<2 > > +@conflict texlive_texmf-buildset-<2018 > > +@conflict texlive_base-<2018p1 > > The last line looks fine but I doubt that you need to copy the other > @conflict lines. Were the -synctex files once provided by one of those > packages?
I looked at what espie@ did with the mktexlsr subpackage. The only conflict that might have conceivably included synctex was teTeX_base, but the synctex source code has copyright starting 2008, and teTeX died in 2006. So, I guess not. > As already discussed, I don't understand how it helps for those depends > to be that strict. Aren't files more commonly moved between > texlive/texmf subpackages, rather than from texlive/base to > texlive/texmf? Unless I'm missing something, we may easily avoid the > problem by only stating minimal versions: less chances for errors and less > churn for pkg_add -u. Please find a diff below. Yep, sounds good. Diff also looks good. So are we saying that, with that change, the diff I posted to move synctex into it's own sub-package would then be good to go (once we fix the merge conflicts that will be caused by your change)? > Well, as mentioned by kili there's also the option to force evince to > always use its internal copy. This means one more copy of synctex to > watch for security/portability issues, but on the other hand this would > decouple evince and texlive updates. Not a bad idea given the recent, > undocumented API/ABI break in libsynctex... > > https://github.com/jlaurens/synctex/issues/23 My gut feeling says we should use the one from TeX live, but I think we should hear from jasper@ and/or aja@, since they are the ones who maintain evince. Guys, what would you prefer? Thanks -- Best Regards Edd Barrett http://www.theunixzoo.co.uk