-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-10-04 11:19, Roman Haefeli wrote: > > Applied to standard paths this would lead to the following search order: > > 1) ~/pd-externals > 2) /usr/local/lib/puredata/extra > 3) /usr/local/lib/pd/extra > 4) /usr/lib/puredata/extra > 5) /usr/lib/pd/extra > > (please add some more, if I forgot some)
please don't add more :-) these are already too many. currently the stdpaths for pd are: 1) ~/pd-externals/ 2) <pd-install-path>/extra/ 3) /usr/local/lib/pd-externals/ note that #3 is not /usr/local/lib/pd/extra/ but really .../pd-externals/ this is there to keep it separate(!) from the case where <pd-install-path> is /usr/local/lib/pd/ the idea is to have some paths independent from <pd-install-path>, where the user (~/pd-externals/) or the sysadmin (/usr/local/lib/pd-externals) can install externals. on debian (where <pd-install-path> is /usr/lib/puredata), there is an additional compatibilty and cross-pd stdpath 4) /usr/lib/pd/extra both pd-vanilla and pd-extended will search this path as a last resort. > to assume that /usr/lib/pdextended/extra should be search first, so that > the patch gets the same 'zexy' as it would get in some other Pd-extended > installation on some other OS. a pdextended specific package would install to /usr/lib/pdextended/extra this path will not be searched by pd-vanilla (nor will pdx search /usr/lib/puredata/extra) fmsdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6K5rgACgkQkX2Xpv6ydvQipwCfdPNhvC0jpV732OTdW8a/7tWU /C4AoOD+dz5XsZMcsmsqDaRs7wyLDWwh =/eA/ -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
