Personal tools
You are here: Home documentation developer GettingIntoPdextended

This page outlines the information about getting a library to be integrated into Pd-extended. The idea is to decentralize the development of Pd-extended as much as possible so that individual developers have as much flexibility as possible without slowing down the release cycle (its slow enough as it is...).



In order to be included in Pd-extended, a library must be:


You can see the list of libraries and their maintainers: Libraries In Pd-extended

  • each library must have an explicit maintainer

  • the maintainer must follow the bug tracker

  • the maintainer must subscribe to pd-dev

  • the maintainer must make sure any commits work on all the build servers

Pd-extended Release Branch

Pd-extended is built and released from a branch in SVN. There is a branch for each release cycle, i.e. 0.43, 0.42, 0.41, etc. Each release branch will start as a copy of the previous release branch, then updates need to be included into it. Each library must be manually copied or merged into the release branch. The recommended process for update a library in the Pd-extended branch is to first make a proper, tested release outside of Pd-extended. Then once you feel that is stable and read for a final release, tag it in SVN, post the tarball to, and copy it into the Pd-extended release branch:

svn co
cd 0.42/externals/ekext
svn log --stop-on-copy    # find the commit number from when things were last copied from trunk for this library
svn merge -r13589:13962
svn ci -m "merged in changes from trunk"

Builds In Between Pd-extended Releases

When in between Pd-extended releases, the large parts of Pd-extended are built directly from trunk in the pure-data SVN. This is a good opportunity to get testing and feedback since commits to trunk are built into the nightly builds each night. This does not mean that all of trunk will be included into the next Pd-extended release branch. That is up to each maintainer to do.

Powered by IEM Powered by Plone Section 508 WCAG Valid XHTML Valid CSS Usable in any browser