Personal tools
You are here: Home documentation developer GettingIntoPdextended
Views

Edit history

Edit: -1 of 1
Time: 2013-08-13 09:19:39
Note: /pd/pd/docs/developer/GettingIntoPdextended/vote

changed:
-
----

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...).

= Requirements =
== library ==
In order to be included in Pd-extended, a library must be:
 *in [Libdir] format with a proper meta file
 *already released as a standalone [Libdir]
 *not dependent on anything not included in Pd-extended
 *listed in the [http://puredata.info/downloads puredata.info downloads page] (add it yourself: [http://puredata.info/docs/AddingYourProjectToDownloads Adding Your Project To Downloads])
 *included in Debian/testing
 *based on the [Library Template]

== maintainer ==
You can see the list of libraries and their maintainers: [http://puredata.info/docs/LibrariesInPdExtended Libraries In Pd-extended]
 *each library must have an explicit maintainer
 *the maintainer must follow the [http://puredata.info/dev/bugtracker bug tracker]
 *the maintainer must subscribe to [http://lists.puredata.info/listinfo/pd-dev 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 http://puredata.info/downloads, and copy it into the Pd-extended release branch:

 *[http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-extended/ Pd-extended release branches]
 *example of merging in changes from trunk
{{{
svn co https://pure-data.svn.sourceforge.net/svnroot/pure-data/branches/pd-extended/0.42
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 https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/ekext
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