On Sat, Nov 14, 2015 at 10:48:16AM +0900, Norbert Preining wrote: > Hi Daniel, > > On Fri, 13 Nov 2015, Daniel Glassey wrote: > > > teckit -- encoding conversion tools > > > libteckit0 -- encoding conversion library > > > (which will be used by perl and python bindings) > > > libteckit-dev -- development files for encoding conversion library > > > > I'm preparing a package for teckit. The compiler part of it, teckit_compile > > is included in texlive-binaries as a static binary. I'm preparing the package > > with the libraries as the libraries can be used by python and perl bindings, > > and there are a couple of other useful binaries too (sfconv and txtconv). > > I see two options: > * you package teckit and we make TeX Live depend on your package > and also your package provides teckit_compile > > * we adjust src:texlive-bin to also build teckit shlibs and dev packages, > in the similar way like libkpathsea and others. Hi Norbert, I prefer the first option as below. > > I'm planning to include the relevant patches from the texlive source. > > That would be great, because otherwise I cannot rely on your > package. If your package includes everything necessary, I will > happily remove the source code of teckit from src:texlive-bin and > use the external library. > > > So, what should we do about teckit_compile? > > we need a replace for the proper version, if you take it over. Fine with me. > > > Would it make sense for texlive-binaries to depend on teckit? > > Sure enough. Great :) > Since teckit is not changing (at all?) this is for sure a no problem. > Other libraries often lag back compared to TL and I cannot use > the Debian packaged parts (libpng esp, but others, too). Most of the changes, which happen rarely, are to update to the current Unicode version, or modify the build system. The package I am building is one commit ahead of the version in the texlive-bin source. It is "Fix 'uninstalled' pkg-config file" which doesn't touch the source of the binaries. > If you prefer to package it yourself, please send it first through > experimental, and when it is accepted into experimental, I prepare > a package for src:texlive-bin and we make a concerted upload. OK, I'll upload it to experimental once it is ready. Shall I make "Debian TeX Maintainers <debian-tex-maint@lists.debian.org>" to be the Maintainer? May I put it in debian-tex git? Regards, Daniel
Attachment:
signature.asc
Description: Digital signature