[PD-dev] pd-extended versioning, svn, and nightly builds

[Hans-Christoph Steiner]

Basically the test builds are all from trunk, except the 'pd' part  
which is from the pd-extended branch.  Once it hits the release cycle,  
then everything is added to the pd-extended branch

You can use rsync, search puredata.info for 'rsync'  or using SVN like  
this:

svn co https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk   
pd-extended
cd pd-extended
rm -r pd
svn co https://pure-data.svn.sourceforge.net/svnroot/pure-data/branches/pd-extended/0.42/pd

.hc

On Sep 23, 2009, at 1:52 PM, Tim Jones wrote:

> Hello
>
> I'd like to know: what is the autobuild server actually building every
> night? What does pd-extended 0.42.5 actually consist of in terms of
> SVN directories? I see /branches/pd-extended/0.42 in svn, but this
> only contains pd source. Are the externals pulled from trunk?
>
> I guess I can get everything that the server builds with rsync this
> way: http://puredata.info/docs/developer/GettingPdSource
> But I would just like to know how to reproduce the nightly pd-extended
> source tree manually from svn. Maybe it's done from one of the many
> files in /scripts, but then where do those come from?
>
> Also, how do the devs keep track of the versions? Is there any history
> kept? Is there any way I could reconstruct 0.42.4 or earlier? I did
> `grep -r "0\.41\.4" *` in the Pd-extended-0.41.4 release, which didn't
> turn up much. Likewise for pd-extended-0.42.5 in the latest rsync
> checkout.
>
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev





----------------------------------------------------------------------------

"[T]he greatest purveyor of violence in the world today [is] my own  
government." - Martin Luther King, Jr.