[PD-dev] Pd-extended EOL?
Hans-Christoph Steiner
hans at at.or.at
Mon Nov 9 14:49:15 CET 2015
Moving towards deken definitely makes sense.
FYI, for anyone interested, it would not be hard to do a Pd-extended update if it is just a matter of updating the libraries.
I think the future of my work on something like Pd-extended would be to make a new standard library that covers lots of stuff. That was really the original idea of Pd-extended, funny enough.
.hc
On Oct 2, 2015, at 8:47 PM, Dan Wilcox wrote:
> Yeah, that’s what I mean. Basically so people will stop downloading an out of date extended if there is an easy way to get the same/similar functionality from a much newer version of vanilla+externals. Judging from the continued extended bug reports of things which are generally fixed in vanilla, I’m thinking it would be a good idea to see what’s needed for a transition and start that more formal conversation.
>
> --------
> Dan Wilcox
> @danomatika
> danomatika.com
> robotcowboy.com
>
>> On Oct 1, 2015, at 4:00 AM, pd-dev-request at lists.iem.at wrote:
>>
>> If by 'relative parity' you mean availability of all the externals the
>> last version of Pd-extended came with, this might have been reached
>> already. Search for 'extended' in deken. It shows a lot of (all?)
>> externals directly packaged from Pd-extended. Many thanks to IOhannes
>> for uploading all those.
>
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at lists.iem.at
> http://lists.puredata.info/listinfo/pd-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20151109/799e4e7c/attachment.html>
More information about the Pd-dev
mailing list