> If I don't do anything in another two weeks I'll > drop it to AUR where it might be better taken care of. What about packages like opencascade[1] that depend on VTK? Also it might take quite a long time to build from AUR. I think it's better to keep it in the community repository as is for now. I might take a look at it and try to fix build issues at some point. [1] https://www.archlinux.org/packages/community/x86_64/opencascade/ -- Andrejs Mivreņiks PGP Key Fingerprint: 3872 5DEB BCA5 9460 09B2 E867 F34B C7DA D782 DAB8 On Sun, 14 Jun 2015, at 15:07, Rashif Ray Rahman wrote: > On 13 June 2015 at 17:33, Simon Hanna <j0k3ing@xxxxxxxxx> wrote: > > On Sat, Jun 13, 2015 at 1:25 PM, Nicola Bizzoca <nicola.bizzoca@xxxxxxxxx> > > wrote: > > > >> Hi, > >> The VTK package present in the community repository is not updated to the > >> last version 6.2.0 http://www.kitware.com/blog/home/post/858 > >> > >> Unfortunately I'm new to Arch and I don't know how to contact the package > >> maintainer > >> > > It is flagged as out of date as you can see here [1] > > I guess the maintainer has his reasons for not updating. Probably > > compatibility with other packages. > > VTK has some open tasks in our bugtracker and, the last time I > checked, does not build as-is for the latest 6.x release. The previous > maintainer did the work on getting 6.x to build so it should be fine > for the time-being. > > Resolving the open issues and updating it will require a bit of time > that I haven't managed but anyone's welcome to help and I'll apply any > necessary changes. If I don't do anything in another two weeks I'll > drop it to AUR where it might be better taken care of. > > > -- > GPG/PGP ID: C0711BF1