This is not a switch in behaviour as I see it, since you can keep things as they are and the behaviour is still the same. Hence, no compatibility breakage here.

Now, if you wanna do things differently, in a new way, as another option, then this is provided and you should adapt your patches.

So it is a matter of deciding wether if it is worth to change your setup or not...

cheers

2018-07-13 11:12 GMT-03:00 Roman Haefeli <reduzent@gmail.com>:
On Thu, 2018-06-14 at 16:32 -0300, Alexandre Torres Porres wrote:
> 2018-06-14 15:35 GMT-03:00 Roman Haefeli <reduzent@gmail.com>:
> > Is this the idea?
>
> Yes! And it's working like that in my tests.

Ok, it's working for me, too. I see significant progress in that (after
having cleared all preferences) I end up with a "working" setup by
clicking myself through the defaults. Things get downloaded to
~/Documents/Pd/externals, which was automatically created added to the
search paths. After installing externals through 'Find externals', I
can load them by [declare -lib <mylib>] and [declare -path <mylib>].

So, does that mean the [declare]-flags -stdlib and -stdpath are
obsolete now?

I can't spot any problems with the branch feature/declare-path, but
virtually all of my patches are broken with it because of incompatible
[declare] flags. I like the 'new way' much better, but I wonder what is
a good path to get there. It's actually an easy thing to replace all
occurences of -stdlib/-stdpath with -lib/path. But switching behaviour
from one version of Pd to the next seems bold.

Roman





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