A place to figure out how the Pd-related packages for Debian/Ubuntu should be structured.

example problems to address

• a package only compatible with puredata: if puredata is at version 0.42.5 and pdextended and desiredata are not at 0.42.5 yet, then there would be an incompatibility in the externals

possible packages

pd

virtual package for libraries to depend on and Pd packages to Provide

pd-common

MIME type, pdsend/pdreceive

puredata

package for Pd vanilla, the code from Miller

pdextended

package for the core of Pd-extended, with the libraries separately packaged

desiredata

package for the core of desiredata, with the libraries separately packaged

pdanywhere

package for the core of pdanywhere (PDa?), with the libraries separately packaged

pd-zexy

packaged library, built against puredata, compatible with anything that provides pd

puredata-foo

packaged library, built against puredata, compatible with only puredata

pdextended-bar

packaged library, built against pdextended, compatible with only pdextended

desiredata-foobar

packaged library, built against desiredata, compatible with only desiredata

pdanywhere-foobar

packaged library, built against pdanywhere, compatible with only pdanywhere

/usr/lib directories for each package

1. a /usr/lib directory for objects that work for everything that provides 'pd'

2. a /usr/lib directory for objects that work only for 'puredata'

3. a /usr/lib directory for objects that work only for 'pd-extended'

4. etc.

discussions

• |PD-dev| adding standard install paths to the 'puredata' package ( first email) ( rest of thread)

• |PD-dev| packaging pd and friends

TODO

• make Help Browser build structure based on libs anywhere in the path. Then the /usr/lib/pd, /usr/lib/puredata, etc. structure can work seemlessly.

• make pd-common