I can think of three ways to make external libraries (externals/abstractions) available on my debian stable (running pd 0.47.1 from the debian repos):
- install the ones from the debian repos
- using the deken plugin
- compiling by hand
I'd rather stick with one to avoid total mess. What do other debian users prefer? Is there a an easy way to include a bunch of directories recursively, rather than adding each of the 30+ paths available in usr/lib/pd/extra/ alone?
I'm trying to find the right balance of control over where what comes from and avoiding too much double work.
Atte
On 9/23/18 8:27 PM, Atte via Pd-list wrote:
I can think of three ways to make external libraries (externals/abstractions) available on my debian stable (running pd 0.47.1 from the debian repos):
- install the ones from the debian repos
- using the deken plugin
- compiling by hand
I'd rather stick with one to avoid total mess. What do other debian users prefer?
with my Debian hat on: the choice should always be to use the Debian repositories, whenever possible. (sometimes this may not be possible, as not all (although most known) Pd-libraries are packaged; or when you need a release of a given library that is newer than Debian/stable).
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
gfmdsar IOhannes
Is there a an easy way to include a bunch of directories recursively, rather than adding each of the 30+ paths available in usr/lib/pd/extra/ alone?
be aware that [declare] and [lib] behavior just changed a bit; they now scan sub-directories of:
- 1 calling patch folder
- 2 paths that you declared in Pd preferences
- 3 standard paths (e.g /usr/lib/pd/extra or ~/.local/lib/pd/extra)
So whatever the way you chose to install "foo" library, i.e whether "foo" folder has been copied locally to the patch, or in "/myHome/myLibs" (provided that you declared "myHome/myLibs" in Pd's path preferences), or in "/usr/lib/pd/extra" (because you used apt-get), all you have to do is put a [declare -path foo] in the calling patch so you can use objects from "foo".
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
Le dim. 23 sept. 2018 à 21:02, IOhannes m zmölnig zmoelnig@iem.at a écrit :
On 9/23/18 8:27 PM, Atte via Pd-list wrote:
I can think of three ways to make external libraries
(externals/abstractions) available on my debian stable (running pd 0.47.1 from the debian repos):
- install the ones from the debian repos
- using the deken plugin
- compiling by hand
I'd rather stick with one to avoid total mess. What do other debian
users prefer?
with my Debian hat on: the choice should always be to use the Debian repositories, whenever possible. (sometimes this may not be possible, as not all (although most known) Pd-libraries are packaged; or when you need a release of a given library that is newer than Debian/stable).
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
gfmdsar IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Sorry, I forgot to say this will only be effective with the version 0.49 to come soon...
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
Le dim. 23 sept. 2018 à 21:48, Antoine Rousseau antoine@metalu.net a écrit :
Is there a an easy way to include a bunch of directories recursively,
rather than adding each of the 30+ paths available in usr/lib/pd/extra/ alone?
be aware that [declare] and [lib] behavior just changed a bit; they now scan sub-directories of:
- 1 calling patch folder
- 2 paths that you declared in Pd preferences
- 3 standard paths (e.g /usr/lib/pd/extra or ~/.local/lib/pd/extra)
So whatever the way you chose to install "foo" library, i.e whether "foo" folder has been copied locally to the patch, or in "/myHome/myLibs" (provided that you declared "myHome/myLibs" in Pd's path preferences), or in "/usr/lib/pd/extra" (because you used apt-get), all you have to do is put a [declare -path foo] in the calling patch so you can use objects from "foo".
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
Le dim. 23 sept. 2018 à 21:02, IOhannes m zmölnig zmoelnig@iem.at a écrit :
On 9/23/18 8:27 PM, Atte via Pd-list wrote:
I can think of three ways to make external libraries
(externals/abstractions) available on my debian stable (running pd 0.47.1 from the debian repos):
- install the ones from the debian repos
- using the deken plugin
- compiling by hand
I'd rather stick with one to avoid total mess. What do other debian
users prefer?
with my Debian hat on: the choice should always be to use the Debian repositories, whenever possible. (sometimes this may not be possible, as not all (although most known) Pd-libraries are packaged; or when you need a release of a given library that is newer than Debian/stable).
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
gfmdsar IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On Sun, 23 Sep 2018 21:02:23 +0200 IOhannes m zmölnig zmoelnig@iem.at wrote:
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
Ok, thanks!.
I just installed 0.48.2 (with my debian hat off), deken is included. I also removed all pd-* debain packages, in an effort to keep s much as possible coming from deken.
However, it seems it's not possible to ask deken which package will provide a certain file (like "apt-file search" in debian). Example: I'm looking through stuff I grabbed from the net to study/modify/learn-from/reuse, and one patch needs avg~. What's the cleanest way of figuring out which (if any) package in deken will provide me with that file?
Cheers
Atte
just search "avg~" in deken, it will answer that you'll find it in "cyclone". (BTW: strangely it will only talk about cyclone-v0.2beta1, not about latest cyclone-v0.3rc1).
Le lun. 24 sept. 2018 à 09:39, Atte via Pd-list pd-list@lists.iem.at a écrit :
On Sun, 23 Sep 2018 21:02:23 +0200 IOhannes m zmölnig zmoelnig@iem.at wrote:
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
Ok, thanks!.
I just installed 0.48.2 (with my debian hat off), deken is included. I also removed all pd-* debain packages, in an effort to keep s much as possible coming from deken.
However, it seems it's not possible to ask deken which package will provide a certain file (like "apt-file search" in debian). Example: I'm looking through stuff I grabbed from the net to study/modify/learn-from/reuse, and one patch needs avg~. What's the cleanest way of figuring out which (if any) package in deken will provide me with that file?
Cheers
Atte
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On Mon, 24 Sep 2018 09:57:58 +0200 Antoine Rousseau antoine@metalu.net wrote:
just search "avg~" in deken, it will answer that you'll find it in "cyclone".
Ah, actually didn't try with exactly "avg~", just a bunch of other objects. I guess that when search doesn't turn up anything, it means it's not provided by any deken package...
Thanks, and sorry for the mistake!
Atte
On 2018-09-24 10:39, Atte via Pd-list wrote:
On Mon, 24 Sep 2018 09:57:58 +0200 Antoine Rousseau antoine@metalu.net wrote:
just search "avg~" in deken, it will answer that you'll find it in "cyclone".
Ah, actually didn't try with exactly "avg~", just a bunch of other objects. I guess that when search doesn't turn up anything, it means it's not provided by any deken package...
the problem is that the "searchobjects" feature was introduced "recently", and the deken packages that want to enable this have to provide a list of objects.
some libraries do provide this list, others don't. so when you are looking for a given object, you might get results or not.
fgmasdr IOhannes
hmm, yeah, I guess we forgot to upload that file to deken :/
Em seg, 24 de set de 2018 às 05:01, Antoine Rousseau antoine@metalu.net escreveu:
just search "avg~" in deken, it will answer that you'll find it in "cyclone". (BTW: strangely it will only talk about cyclone-v0.2beta1, not about latest cyclone-v0.3rc1).
Le lun. 24 sept. 2018 à 09:39, Atte via Pd-list pd-list@lists.iem.at a écrit :
On Sun, 23 Sep 2018 21:02:23 +0200 IOhannes m zmölnig zmoelnig@iem.at wrote:
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
Ok, thanks!.
I just installed 0.48.2 (with my debian hat off), deken is included. I also removed all pd-* debain packages, in an effort to keep s much as possible coming from deken.
However, it seems it's not possible to ask deken which package will provide a certain file (like "apt-file search" in debian). Example: I'm looking through stuff I grabbed from the net to study/modify/learn-from/reuse, and one patch needs avg~. What's the cleanest way of figuring out which (if any) package in deken will provide me with that file?
Cheers
Atte
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 2018-09-24 15:26, Alexandre Torres Porres wrote:
hmm, yeah, I guess we forgot to upload that file to deken :/
when using the "deken" cmdline tool (well, a recent enough version) for packaging/uploading, the default package-format (dekformat=1) will already take care of this.
packagers can chose to use the old format (dekformat=0) for compatibility with older deken-plugin versions, but then they won't get this feature. Pd-0.49 comes with a very recent deken-plugin; users of older deken-plugins are asked to upgrade their plugin in the least annoying and most persistent way i could imagine (which might be more annoying and less obvious than i wish for); so i think that packagers really should switch to dekformat=1.
fgamdfr IOhannes
On 2018-09-24 09:39, Atte via Pd-list wrote:
On Sun, 23 Sep 2018 21:02:23 +0200 IOhannes m zmölnig zmoelnig@iem.at wrote:
there is also the "pd-deken-apt" (Debian) package, which allows you to install the Debian packaged libraries from within Pd (using the deken plugin)
Ok, thanks!.
I just installed 0.48.2 (with my debian hat off), deken is included. I also removed all pd-* debain packages, in an effort to keep s much as possible coming from deken.
weird. why would you do exactly the opposite of what i suggested? also, Pd-0.48-2 is available for Debian/stretch via backports.
gmfasdr IOhannes
On Mon, 24 Sep 2018 10:12:14 +0200 IOhannes m zmoelnig zmoelnig@iem.at wrote:
weird. why would you do exactly the opposite of what i suggested? also, Pd-0.48-2 is available for Debian/stretch via backports.
Oops, sorry bout that, I totally misunderstood you, then. My bad.
So you would suggest pd from backports!
How about externals/abstractions (is this referred to as "packages" or "libraries"?)? If I stick to debian repos here, is there a simple way to add all these to the search path in pd? It seems cumbersome and error prone to add each path by hand, although I guess I could script it...
Cheers
Atte
On 2018-09-24 10:36, Atte via Pd-list wrote:
On Mon, 24 Sep 2018 10:12:14 +0200 IOhannes m zmoelnig zmoelnig@iem.at wrote:
weird. why would you do exactly the opposite of what i suggested? also, Pd-0.48-2 is available for Debian/stretch via backports.
Oops, sorry bout that, I totally misunderstood you, then. My bad.
i probably was not very clear in what i was saying :-)
So you would suggest pd from backports!
well, it's probably the main reason why the backports package is *there*.
How about externals/abstractions (is this referred to as "packages" or "libraries"?)? If I stick to debian repos here, is there a simple way to add all these to the search path in pd? It seems cumbersome and error prone to add each path by hand, although I guess I could script it...
you simply shouldn't. instead use [declare] to declare dependencies on all packages your patch requires. (i haven't heard of a feature for Python to import all the libraries; or for C/C++ to include all the headers; there must be some reasoning there...)
fgas,dr IOhannes
On Mon, 24 Sep 2018 11:17:18 +0200 IOhannes m zmoelnig zmoelnig@iem.at wrote:
How about externals/abstractions (is this referred to as "packages" or "libraries"?)? If I stick to debian repos here, is there a simple way to add all these to the search path in pd? It seems cumbersome and error prone to add each path by hand, although I guess I could script it...
you simply shouldn't. instead use [declare] to declare dependencies on all packages your patch requires. (i haven't heard of a feature for Python to import all the libraries; or for C/C++ to include all the headers; there must be some reasoning there...)
Ok, great, I'll have to look into that!
Thanks!!
Atte
When I work on something bigger, I put my externals in the same dir with my patches . Some of the externals may be originally installed from a Debian repo, some from Deken, some compiled. I find the externals that I need and that work. Then, I just copy the externals to my patch dir to keep things in order. This way I know exactly what I have and I can redistribute the files between computers.
I also keep a specific Linux distro and a specific version of puredata. I don't update until I'm ready to face problems that come with updating (changes in features, behaviour, regressions, etc) - which might mean that the patches need to be rewritten in.
On Sun, Sep 23, 2018, at 8:27 PM, Atte via Pd-list wrote:
I can think of three ways to make external libraries (externals/ abstractions) available on my debian stable (running pd 0.47.1 from the debian repos):
- install the ones from the debian repos
- using the deken plugin
- compiling by hand
I'd rather stick with one to avoid total mess. What do other debian users prefer? Is there a an easy way to include a bunch of directories recursively, rather than adding each of the 30+ paths available in usr/ lib/pd/extra/ alone?
I'm trying to find the right balance of control over where what comes from and avoiding too much double work. -- Atte
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Alexandre Torres Porres -
Antoine Rousseau -
Atte -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Kaj Ailomaa