<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>There are different core versions of pd: vanilla (miller's), devel, extended, desiredata. Then there are all of the externals, docs, etc. Pd-extended includes all this stuff as part of each release so everything is then added to the pd-extended release branch. The externals, docs, etc. in the Pd-extended release branch then gets tweaks to make sure it all works well together as a package.</div><div><br></div><div>So if you want the whole tested, integrated Pd-extended package, you should use everything from the Pd-extended release branches.</div><div><br></div><div>.hc</div><br><div><div>On Aug 12, 2009, at 8:04 PM, Tim Jones wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">As the Gentoo pd-overlay is a little moldy, I was planning on fixing some up some of the ebuilds. I was a little bit confused by all the overlap in svn, though. What's the difference between the trunk and the pd-devel branch? pd-overlay also seemingly offers two choices: build pd-extended (with all its externals) in one process, or build pd-devel (or a numbered version of pd, src from M. Puckette's site) and then build the plugins seperately, one by one. Would there be any significant difference between these two approaches? I like the modularity of the latter, having seperate ebuilds for each plugin. Also, what would be the best place in svn to get src for the externals themselves? /trunk/externals?<br> <br> _______________________________________________<br>Pd-dev mailing list<br><a href="mailto:Pd-dev@iem.at">Pd-dev@iem.at</a><br><a href="http://lists.puredata.info/listinfo/pd-dev">http://lists.puredata.info/listinfo/pd-dev</a><br></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div><br class="Apple-interchange-newline"><br class="khtml-block-placeholder"></div><div><br class="khtml-block-placeholder"></div><div><br class="khtml-block-placeholder"></div><div>----------------------------------------------------------------------------</div><div><br></div><div>Programs should be written for people to read, and only incidentally for machines to execute.</div><div> - from Structure and Interpretation of Computer Programs</div></span> </div><br></body></html>