request sponsor/upload for pd-pdstring

[Roman Haefeli]

Hi again

There was some confusion on my part, since I seem to have tested it only
in Debian stable where everything works as expected. The puredata
package in Debian unstable is quite different from previous versions and
also is its behavior.

On Fri, 2011-09-30 at 17:02 +0200, IOhannes m zmölnig wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 09/30/2011 04:19 PM, Roman Haefeli wrote:
> > On Fri, 2011-09-30 at 13:24 +0200, IOhannes m zmölnig wrote:
> >> debian/control:
> >>  any reason why you are so picky about the debhelper version?
> > 
> > I'm using short-form dh with dh overrides. Lintian tells me that those
> > features are only available since 7.0.50. I read the thread about
> 
> thanks for the explanation.
> 
> > 
> >> debian/README.Debian
> >>  quite a long line :-)
> >>  more important, i cannot load pdstring following your advice in
> >> README.Debian: [declare -stdlib extra/pdstring] will do nothing (on
> >> reload), only [declare -lib pdstring] helps
> > 
> > How did you test? The '-lib' flag searches relative to your patch,
> > whereas '-stdlib' searches relative to pd. You only can correctly test
> > it by effectively installing the package and run pd (/usr/bin/pd).
> 
> my test is to open the attached abstraction with
> $ puredata -noprefs pdstring-test.pd
> which gives me:
> <snip>
>  any2string
> error: ... couldn't create
> </snip>
> 
> puredata (the 0.43.0-4) finds neither the library nor the abstraction of
> the name "any2string".
> 
> the former can be a bug in your documentation (i have to admit that i'm
> not so familiar with [declare]), as it would look for a library
> "extra/pdstring" where the pdstring.pd_linux file really is
> extra/pdstring/pdstring.pd_linux, so it should probably read "-stdlib
> extra/pdstring/pdstring".

'-stdlib extra/pdstring/pdstring' is supposed to work as well but should
not be necessary at all. Pd normally checks also folders with the lib
name for libs. When specifying mylib, both extra/mylib.pd_linux and
extra/mylib/mylib.pd_linux are searched. 

> > However, it turned out, that the advice was not complete, since the
> > library also contains abstractions, which are not found with only
> > '-stdlib extra/pdstring'. The full and correct declaration is:
> > 
> > [declare -stdlib extra/pdstring -stdpath extra/pdstring]
> > 
> > Yeah, that's a lot for loading only a library, but unfortunately that is
> > how it currently works in Pd.
> 
> after closer inspection it seems like this _might_ be a bug in the
> "puredata" package, which seems only to consider "/usr/lib/puredata/" as
> a stdpath, and it won't search "extra/pdstring" in "/usr/lib/pd".
> 
> i'm not entirely sure though (given the nastiness of [declare])
> if you think that it is a bug in "puredata-core", please file a bugreport.

Yeah, that is indeed the case. Before filing a bug report, I'd like to
clear up the meanings of the different paths.

/usr/lib/pd/extra
  Am I right in assuming that this path is supposed to be searched by
  all flavors of Pd (all packages that provide the virtual package pd)?
  This also the path where usually external libraries are installed to 
  because from there they can be loaded from any flavor of pd?

/usr/lib/puredata/extra
  is only searched by puredata / pd from the puredata package?
  This is where libraries are installed that only are suitable for
  the pd provided by the puredata package?
  
/usr/lib/pd-extended/extra
  is only searched by pdextended / pd from the pd-extended package?
  Libs that are only useful with pdextended go there?

If that is the case, then there is definitely a bug in the puredata-core
package as it is ignoring /usr/lib/pd/extra.

This also means, that currently all Pd libraries in unstable that
install to /usr/lib/pd/extra (most of them do) are currently broken, as
there is no proper way to actually load them in pd (you still can
specify the absolute path to the library, which renders your patch
unportable to other OS').

Roman