|
Or perhaps upstream should re-think its release strategy. How do
they expect the scientific community to keep up with so frequent
major versions, I wonder? Anyway.
Meanwhile, let's keep in mind that our distribution of VTK packages
is here to serve existing packages making use of it (such as
Paraview for instance). Unless one of these packages suddenly
requires a minimum VTK version higher than 7, there is no urgency in
providing more up-to-date versions.
Ghis
Le 25/11/17 à 15:27, Nico Schlömer a
écrit :
Thanks Gert for the ping; hopfully they'll get to
it soon.
On a related note, VTK has bumped its version to 9.0.0 in
master [1], so it looks like soon we'll have to catch up with
three (!) major versions. (Perhaps we'll have to rethink how
we package vtk for debian.)
Cheers,
Nico
Hello Nico,
Am Dienstag, den 07.11.2017, 13:12 +0000 schrieb Nico
Schlömer:
> VTK7 is in NEW for two months again with no indication of
when it
> will be through.
Well it is a big package, and it came also with an ITP.
> I need VTK for my work and would like to start tweaking
the package,
> especially since xdmf3 landed in
d/copyright::Files-Excluded. (No
> idea why.)
This is there for some time already, longer then I have been
touching
this package, but for some reason it is not enabled to use the
system
version neither, I think there is some bug.
> I'm not sure if it's a good idea to mess with the package
while in
> NEW though. What do you usually do in such situations?
If I just need the packages for myself, then I create a local
version
that might be uploaded as soon as the pakage has cleared the
NEW
pipeline.
Anyway, I'll ping the FTP-master that rejected it the first
time.
Best,
Gert
|