A core idea of having a standard format for libraries is to make them easily packaged and distributed. There are lots of libraries that follow https://puredata.info/docs/developer/LibraryTemplate, so the next step is for someone to make something like https://pypi.python.org as the central repo of libraries that includes an update/download tool.
As for the auto-build servers, I think only the Debian ones are still running. The Windows one was on a server that died, and the OSX was an old laptop that is basically dead. It was running 10.5 anyway. For anyone who can set up a Windows and/or OSX build machine, they were super helpful for maintaining cross-platform compatibility. Here are the docs: http://puredata.info/docs/developer/WindowsMinGW http://puredata.info/docs/developer/MacOSXFink These all have some info, but need work: http://puredata.info/docs/developer/MacOSXMacPorts http://puredata.info/docs/developer/Windows64BitMinGWX64 http://puredata.info/docs/developer/MacOSXHomebrew .hc Dan Wilcox wrote: > I like the idea of being able to download vanilla and then download other > externals as needed, Gem for instance. Currently, I've been copying in the > prebuilt externals from Pd extended to use with newer versions of vanilla. > > Of course, this wouldn't be needed if we could set up more of a concerted > release schedule to crank out newer versions of extended. I also like the > work Hans et al. did for pixel perfect patches across platforms. I'd like to > see that incorporated into vanilla as it makes sense. > > I see the autobuild server is still up. Does this still build for all > platforms? > > On Sep 29, 2014, at 8:44 PM, pd-list-requ...@lists.iem.at wrote: > >> From: sebfumas...@aol.com >> Subject: Re: [PD] Updated Pd-Extended >> Date: September 29, 2014 at 6:10:42 PM EDT >> To: pd-list@lists.iem.at >> >> >> Hello again list, >> >> What do y'all think of the idea of releasing Pd-extended both as a >> "core" pd with no libraries added except maybe the libdir and hex loaders >> and as a version with multiple libraries (2 release stages)? Perhaps it's >> been discussed. the thing I enjoy about Extended is the features it adds to >> pd-vanilla, and this way people can just keep the same libraries installed >> in the same places and switch between vanilla and extended easier. In my >> experience I never need/want to use most of the arbitrary libraries included >> and/or loaded on startup and could easily download and install the ones I do >> want. I also see the appeal/logic of using a standardized set of libs though. >> >> seems like a reasonable way to develop it too... everyone focusing on the >> core and then working on their own libs for a bundled release. >> >> Also about import/saving libraries to load on startup: wouldn't it make more >> sense if either the list were editable or there were no list? Strange that >> users get this arbitrary list to load on startup, (not even all the libs >> included in PdX) without being able to edit it, a set of libs that they >> never have to [import], but then they're expected to [import] everything >> else unless they manually edit the preferences file (quite confusing for >> most users)? >> >> Btw I also have a bit of time and know a little bit of c and tcl, i'd be >> glad to pitch in where i can when there is a concrete plan (list of to-do's) >> of how to move forward with Pd-extended. >> >> -Sebastian > > -------- > Dan Wilcox > @danomatika > danomatika.com > robotcowboy.com > > > > > > > > N�n�r����)em�h�yhiם�w^�� > _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list