On Wed, Jun 08, 2016 at 02:08:59PM +0200, Ludwig Nussel wrote:
Christoph Grüninger schrieb:
[...] Asking my question in a different way: Is there a reason not to update Tex Live? What actions should I perform to promote such an update?
texlive may look like a bunch of harmless add-on packages but it's actually integrated quite deep in the OS as many packages rely on it for building documentation. So a new texlive version has the potential to cause collateral damage in other packages. I'm not opposed to the update and in fact I think it makes sense. Someone has to go ahead and submit from Factory to 42.2. We can put texlive in a separate staging project to see what happens. You need the support or at least agreement with the package maintainer, as well as volunteers to help fix the potential breakage.
I'm currently working on TeXLive 2016 ... nevertheless this takes time as generating the spec files isn't an easy task. Also building and testing takes some time on 6000 packages as well :) And no, I've not yet submitted to Factory nor any other repository. Also submitting to Leap needs some perl packages updates as well to get biblatex-biber-2.4 working as well. This might cause some other side effects. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr