[Pkg-octave-devel] [sloisel@gmail.com: Call for rpm/deb/binary packagers for Workshop]

[Thomas Weber]

Hi, 
> I do not think that uploading a package will hurt.  We might upload it to
> experimental or, in the case it reaches unstable and is in a bad state,
> we could fill an RC bug report to prevent its migration into testing.

Ok, I started with it. However, octave-workshop produces one binary
which links directly to Octave's .so files:

$ ldd octave-workshop
  liboctinterp.so => /usr/lib/octave-2.1.73/liboctinterp.so (0xa6e6c000)
  liboctave.so => /usr/lib/octave-2.1.73/liboctave.so (0xa688a000)

(octave-workshop gets an rpath of /lib:/usr/lib/octave-2.1.73/ during
build; /lib comes from QT4, but the other rpath comes from mkoctfile's
RLD_FLAG)

This means a new version of octave-workshop for every new version of
Octave 
  => I guess we should solve #367165 (libs in /usr/lib/) at some point.

	Thomas