Re: octave vs tigervnc fltk battle

[Greg Troxel <gdt%lexort.com@localhost>]

Ramiro Aceves <ea1abz%gmail.com@localhost> writes:

> Installation of octave package removes fltk13  library and breaks tigervnc.
>
> netbsd-nuc# pkgin in octave
> calculating dependencies...done.
>
> 1 package to install:
>   fltk-1.4.5nb1
>
> 1 package to remove:
>   fltk13-1.3.11nb2

> Is a bug that should me fixed in pkgsrc?

Well, it's a pile of bugs, some blend of things, each of which I have no
idea if it's true:

  - 1) fltk should have good enough compat that maintained programs don't
    need to use old versions
  - 2) tigervnc upstream should have a release that works with the most
    recent release of fltk

and

  - 3) Perhaps pkgsrc should allow installing two versions of fltk, but
    that's a lot of work, and ick imposed on the system.  It's not clear
    it's worth it, only that nobody has done it.

(1) is intractable, from the pkgsrc viewpoint.  But, I suggest you look
at fltk upstream and see if pkgsrc has the latest release.  If not,
prepare an update in wip.

(2) I have no idea what's going on.  I suggest that you look into it,
finding out if pkgsrc has the latest release.  If not, prepare an update
in wip.  If so, see if it can build with fltk1.4.  See what upstream
docs (README or install instructions linked from README) say about what
version it needs.  Also look at their autoconf/cmake/whatever to see
what it checks for.

  - If upstream docs are not clear (you can't definitely answer the
    question from the docs), file a bug about that.
  - If the latest release doesn't work with the latest fltk, file a bug
    about that.
  - If there hasn't been a release in 2 years, and there's activity,
    especially if master/whatever works with newer fltk, file a bug that
    a release is overdue.
  - If there hasn't been a release and there's not really activity, file
    a bug that it appears unmaintained, asking for status to be updated.

We can then drop these bug refs in the package.


So basically my answer is that there might be an issue in pkgsrc, but it
is far more likely that this reflects upstream woes.  Someone who cares
(which means they want to use octave and tigervnc both!) will have to
dig in.  Probably that set of people is you.