[PD] Pd-extended 0.42.5 release candidate 6 released!

[Ed Kelly]

Perhaps for those of us who already know our way around the unix filesystem and 
PD libraries, we could just

sudo cp -r /usr/lib/pd/extra/* /path/to/pdextended

...or perhaps just add /usr/lib/pd/extra to the startup path.

I think if one knows how to compile an extern it's probably a safe bet that one 
knows how to link, copy, sudo etc.

Perhaps in fact, the best way to deal with this is to put some lines like:
"
If you are using externals you have compiled yourself, you may want to put the 
following path into the startup paths from File->Path... (Linux / Windows) or 
PD->Settings...->Path... (Mac OSX):

/usr/lib/pd/extra
"

...into the Readme.html file.

Metastudio 3 for Pure Data - Free download at:
http://sharktracks.co.uk/puredata



----- Original Message ----
From: Roman Haefeli <reduzent at gmail.com>
To: Hans-Christoph Steiner <hans at at.or.at>
Cc: Pd List <pd-list at iem.at>
Sent: Thu, 16 September, 2010 8:22:18
Subject: Re: [PD] Pd-extended 0.42.5 release candidate 6 released!

On Wed, 2010-09-15 at 18:57 -0400, Hans-Christoph Steiner wrote:
> When people use Pd-extended 0.42.5, they expect that certain libraries
> will be there, and they will be a certain version.  For example
> Pd-extended 0.42.5 includes Gem 0.92.3.  So you can say "my patch works
> with Pd-extended 0.42.5" and it'll work with any installation of
> Pd-extended 0.42.5.

I totally got that. And I never meant to put that in question. 

> If Pd-extended 0.42.5 also looks at /usr/lib/pd, then someone could
> install Gem 0.93 there and Pd-extended would use it.  Let's say Gem 0.93
> introduces an obscure bug which breaks your patch.  Then someone who has
> installed Pd-extended 0.42.5 can no longer be sure that the patch will
> always work with Pd-extended 0.42.5.

That's why I proposed to put the path /usr/lib/pd/extra last in the
order. So Pd-extended would still load it's own Gem and not the manually
installed one. It's really *_only_* about making it easier to load
libraries that are *_not_yet_* part of Pd-extended while at the same
time not interfere with the libraries that are already part of
Pd-extended. I hope I could make myself clear now.


Roman



_______________________________________________
Pd-list at iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list