It would be a good idea to version it, if possible. I’m not sure if the meta package has been created yet, but that’s the idea. -------- Dan Wilcox @danomatika <https://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/> > On Oct 14, 2015, at 7:54 PM, Jonathan Wilkes <jancs...@yahoo.com> wrote: > > Will the pd-extended package be versioned as well? In other words is it a > rolling package release-- always fetching the most recent versions of the > library packages it contains, or standard release-- tested and released with > specific versions of the library packages? > > -Jonathan > On Wednesday, October 14, 2015 6:11 PM, Dan Wilcox <danomat...@gmail.com> > wrote: > > > Well, not specifically me as I haven’t contributed code to deken. Versions > are currently handled by the filename format: > https://github.com/pure-data/deken#create-and-upload-a-package > <https://github.com/pure-data/deken#create-and-upload-a-package> > > -------- > Dan Wilcox > @danomatika <https://twitter.com/danomatika> > danomatika.com <http://danomatika.com/> > robotcowboy.com <http://robotcowboy.com/> >> On Oct 14, 2015, at 3:07 PM, Jonathan Wilkes <jancs...@yahoo.com >> <mailto:jancs...@yahoo.com>> wrote: >> >> Hi Dan, >> How do you handle versioning? >> >> >> >> >> >> On Wednesday, October 14, 2015 3:18 PM, Dan Wilcox <danomat...@gmail.com >> <mailto:danomat...@gmail.com>> wrote: >> >> >> That’s why one idea with deken is to install an “extended” meta package >> which installs most (if not all) of the libs that came with pd-extended. I >> don’t think it’s too hard to ask a user to open the plugin and install a >> single package. >> >> Also, the cross platform issue will be fixed in time. Thanks for debugging! >> >> -------- >> Dan Wilcox >> @danomatika <https://twitter.com/danomatika> >> danomatika.com <http://danomatika.com/> >> robotcowboy.com <http://robotcowboy.com/> >>> On Oct 14, 2015, at 9:22 AM, ro...@dds.nl <mailto:ro...@dds.nl> wrote: >>> >>> >>> it looks like the future of pd-extended is going to be 'deken'. >>> what to do then about portability? >>> >>> i make patches for people who don't know a lot about programming. >>> plus they are on Mac, i'm on Windows. >>> one time downloading the right version of Pdext is enough; >>> i can give them my patches and they just run them. >>> when i make changes, new features: there's no hassle for them. >>> >>> using Vanilla & deken is something else. >>> declaring a library in the patch is not enough. >>> including the library in the patch-package works only on the same type of >>> OS; >>> Windows & Windows, Mac & Mac, (Linux & Linux?). >>> >>> one method could be a deken-connected feature to automatically download a >>> declared lib when it's not present. >>> what about updates or changes in a lib in that case? >>> >>> the organisation of pd-ext somehow included a kind of gate-keeping, which >>> resulted in a stable Pd-system. >>> i'm still using Pdext 42.5 and the included libs a lot (because of the old >>> machines in my installations). the same libs are functional in Pdext 43.4. >>> so one could argue that there's no great need for a portability design. >>> just download everything that's necessary (and available) and it will work >>> for quite some time. >>> >>> ? >>> rolf >> >> >> >> _______________________________________________ >> Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list >> <http://lists.puredata.info/listinfo/pd-list> >> >> > > >
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
