A minimal package management system for Pure Data externals.

Packages are stored on http://puredata.info/ and can be installed using the Help -> Find Packages menu after installing the TCL plugin.

Click to download deken-plugin.tcl and save it to your Pd folder:

• Linux = ~/pd-externals/deken-plugin/
• OSX = ~/Library/Pd/deken-plugin/
• Windows = %AppData%\Pd\deken-plugin\

Then select Help -> Find Packages and type the name of the external you would like to search for.

The deken-plugin will help you find and install Pd-libraries. However, it does not verify whether a given package is downloaded from a trusted source or not.

As of now, the default package source is http://puredata.info. Anybody who has an account on that website (currently that's a few thousand people) can upload packages, that the deken-plugin will happily find and install for you.

In order to make these packages more trustworthy, we ask people to sign their uploaded packages with the GPG-key. Unfortunately the deken-plugin does not check these signatures yet. If you are concerned about the authenticity of a given download, you can check the GPG-signature manually, by following these steps:

• Navigate to Help -> Find Packages and search for an external
• Hover your mouse over one of the search results
• At the bottom of the search window, a download link will appear
• Remember this link! (e.g. http://puredata.info/Members/the-bfg/software/frobscottle-1.10-externals.zip)
• Append .asc to the link (e.g. http://puredata.info/Members/the-bfg/software/frobscottle-1.10-externals.zip.asc)
• Download the GPG-signature from the link (besides the downloaded archive)
• Run gpg --verify on the downloaded file

If the signature is correct, you can decide yourself whether you actually trust the person who signed:

• Do you trust the signature to be owned by the person?
• Do you know the person?
• Do you trust them enough to let them install arbitrary software on your machine?

You can use the deken command line tool to create packaged zipfiles with the correct searchable architectures in the filename, for example freeverb~-v0.1-(Linux-amd64-64)-externals.zip.

If you don't want to use the deken packaging tool you can zip and upload the files yourself. See the "Filename format" section below.

$ curl https://raw.githubusercontent.com/pure-data/deken/master/deken > ~/bin/deken
$ chmod 755 ~/bin/deken
$ deken
This is your first time running deken on this machine.
I'm going to install myself and my dependencies into ~/.deken now.
Feel free to ctrl-C now if you don't want to do this.
...

See config.md for deken's configuration file format.

You have a directory containing your compiled externals object files called my_external.

This command will create a file like my_external-v0.1-(Linux-amd64-64)-externals.zip and upload it to your account on http://puredata.info/ where the search plugin can find it:

$ deken package -v 0.1 my_external
$ deken upload my_external

You can also just call the 'upload' directly and it will call the package command for you in one step:

$ deken upload -v 0.1 my_external

The upload step will also generate a .sha256 checksum file and upload it along with the zip file.

The deken tool names a zipfile of externals binaries with a specific format to be optimally searchable on puredata.info:

NAME[-VERSION-](ARCH1)(ARCH2)(ARCHX...)-externals.zip

• NAME is the name of the externals package ("zexy", "cyclone", "freeverb~").
• -VERSION- is an optional section which can contain version information for the end user.
• (ARCH1)(ARCH2) etc. are architecture specifiers for each type of architecture the externals are compiled for within this zipfile.

Note that the zipfile should contain a single directory at the top level with NAME the same as the externals package itself. For example a freeverb~ externals package would contain a directory "freeverb~" at the top level of the zipfile in which the externals live.

The square brackets around the "-VERSION-" section are to indicate it is optional, don't include them. The round braces "(" around architectures are included to separate the architectures visibly from eachother.

Some examples:

freeverb~(Windows-i386-32)-externals.zip
freeverb~(Linux-armv6-32)-externals.zip
cyclone-0.1_alpha57(Linux-x86_64-64)-externals.zip
freeverb~(Darwin-i386-32)(Darwin-x86_64-32)(Linux-armv6-32)-externals.zip

$ deken upgrade
... self upgrades the scripts ...

$ deken -h

OSX Example

$ deken --platform
Darwin-i386-64bit

Linux example

$ deken --platform
Linux-x86_64-64bit-ELF

Raspbian

$ deken --platform
Linux-armv6l-32bit-ELF