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): > > 1) install the ones from the debian repos > 2) using the deken plugin > 3) 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 > > http://atte.dk http://a773.dk > > > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
