[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Skip VTK7 and go directly VTK8? Was: Re: vtk6 and vtk7



Alright, then let's tackle VTK7 first. Changes look good to me; if you want to upload, that'd be fine by me.

Cheers,
Nico

On Wed, Jul 12, 2017 at 12:40 PM Gert Wollny <gw.fossdev@gmail.com> wrote:
Am Mittwoch, den 12.07.2017, 07:41 +0000 schrieb Nico Schlömer:
> I've pushed my changes for the Python 3 in the vtk7 repo. If you want
> to upload it, or first move it all to vtk8 and upload that, that'd be
> fine by me.

I had a short look at vtk8, and it will need more work to get it ready
than expected, because they added more third party libraries that are
also available in Debian, without even trying to make it easy to use
the system variant.

Since with this upload we face two big changes, i.e. vtk-opengl2 and
python3, I have to concede that it is better to do an upload ASAP to
make it possible that the maintainers of the reverse dependencies can
decide whether they move forward with porting or remain with VTK6.

Please pull the changes because I've added you to the uploaders and had
to change some dependencies to python3-*.

Thanks for your contribution,
Gert

> We could then go ahead and try to resolve the python conflicts.
>
> Cheers,
> Nico
>
> On Tue, Jul 11, 2017 at 10:52 PM Nico Schlömer <nico.schloemer@gmail.
> com> wrote:
> > > or you can push changes to make
> > > it python3, and then we resolve the conflicts while it is in
> > > experimental.
> >
> > I'll do that tomorrow.
> >
> > Cheers,
> > Nico
> >
> > On Tue, Jul 11, 2017 at 10:19 PM Gert Wollny <gw.fossdev@gmail.com>
> > wrote:
> > > Am Dienstag, den 11.07.2017, 20:02 +0000 schrieb Nico Schlömer:
> > > > > However, for the name xxxx-vtk we have packages in oldstable
> > > > > that refers to the vtk5 python and tcl bindings.
> > > >
> > > > Ah right, I faintly remember that too. Are those ever going to
> > > go
> > > > away?
> > > I think one can actually set the conflicts and replaces properly
> > > to
> > > allow upgrading oldstable-stable-buster, and AFAIK a direct
> > > upgrade
> > > from oldstable to testing doesn't need to be supported.
> > >
> > >
> > > > Indeed. It may be a pick-your-poison situation: Either don't
> > > have any
> > > > Python 3 interfaces, or get conflicting packages. (The
> > > egomaniac that
> > > > I am I'd vote for the latter.) Anyhow, we can try and
> > > consolidate
> > > > those two. Not sure if possible.
> > > I had a look through the conflicting files, and for pyhon there
> > > were
> > > not many (pvtk and pvtkython come to mind). 
> > >
> > >
> > > > Gert, are you already done with your iteration on the package?
> > > If
> > > > yes, and the coinstallability is the only remaining issue, we
> > > could
> > > > start working at this in the vtk8 repo.
> > > I am done, I could upload with python2, or you can push changes
> > > to make
> > > it python3, and then we resolve the conflicts while it is in
> > > experimental.
> > >
> > > thanks,
> > > Gert
> > >
> > >

Reply to: