I feel like the easiest method is to leave the main deken development in the separate repo and pull in periodic versions/updates upstream. So a good call for deken versioning. :)
Maybe another option is deken can be a submodule in the repo pure-data? This approach has helped libpd be a bit more maintainable by having pure-data as a submodule.
-------- Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Mar 22, 2016, at 5:00 AM, pd-dev-request@lists.iem.at wrote:
From: Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu> Subject: Re: [PD-dev] [pure-data:pure-data] 2 new commits to pure-data Date: March 21, 2016 at 5:35:05 PM MDT To: IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> Cc: PureData developer's list <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at>
Hmm... OK, reverting. I now would like to know where to track this from (or should I just leave it and have people submit patches to it in the pd repo instead?)
I'm happy to simply track it by hand (it's just one file). But I don't know how to identify the "latest version" - just hitting "download" gave me something that Hannes thinks is older than the version I had before. Ideally I should grab a good version from github and store its commit number somewhere for future reference.
cheers M
On Tue, Mar 22, 2016 at 10:33:33AM -0600, Dan Wilcox wrote:
I feel like the easiest method is to leave the main deken development in the separate repo and pull in periodic versions/updates upstream. So a good call for deken versioning. :)
Maybe another option is deken can be a submodule in the repo pure-data? This approach has helped libpd be a bit more maintainable by having pure-data as a submodule.
Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Mar 22, 2016, at 5:00 AM, pd-dev-request@lists.iem.at wrote:
From: Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu> Subject: Re: [PD-dev] [pure-data:pure-data] 2 new commits to pure-data Date: March 21, 2016 at 5:35:05 PM MDT To: IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> Cc: PureData developer's list <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at>
Hmm... OK, reverting. I now would like to know where to track this from (or should I just leave it and have people submit patches to it in the pd repo instead?)
Maybe the new development is in a diff branch?
The “Download” button has become problematic, mainly in that the generated zips/tarball does not check out submodules. I resort to providing my own zip link for workshop repos, etc … :(
-------- Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Mar 22, 2016, at 10:51 AM, Miller Puckette msp@ucsd.edu wrote:
I'm happy to simply track it by hand (it's just one file). But I don't know how to identify the "latest version" - just hitting "download" gave me something that Hannes thinks is older than the version I had before. Ideally I should grab a good version from github and store its commit number somewhere for future reference.
cheers M
On Tue, Mar 22, 2016 at 10:33:33AM -0600, Dan Wilcox wrote:
I feel like the easiest method is to leave the main deken development in the separate repo and pull in periodic versions/updates upstream. So a good call for deken versioning. :)
Maybe another option is deken can be a submodule in the repo pure-data? This approach has helped libpd be a bit more maintainable by having pure-data as a submodule.
Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Mar 22, 2016, at 5:00 AM, pd-dev-request@lists.iem.at wrote:
From: Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu> Subject: Re: [PD-dev] [pure-data:pure-data] 2 new commits to pure-data Date: March 21, 2016 at 5:35:05 PM MDT To: IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> Cc: PureData developer's list <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at>
Hmm... OK, reverting. I now would like to know where to track this from (or should I just leave it and have people submit patches to it in the pd repo instead?)
On 03/22/2016 05:53 PM, Dan Wilcox wrote:
Maybe the new development is in a diff branch?
i think there are three options: whenever the deken devs are positive that a version of the deken-plugin should be included in Pd-mainstream, - the deken devs create a Pull Request in the pure-data repository - the deken devs push @millerpuckette, asking to pick the current deken-plugin.tcl (doesn't require switching repos) - there is a separate "pd-deployment" branch in the deken repository, where only "ready to be included" versions of the plugin are found. it's always safe to include the latest version of this branch into Pd.
as for tagging: i'm not sure, mainly because deken consists of two components (the plugin and the cmdline upload-tool). since the plugin has been included into Pd-mainstream, focus has shifted considerable towards the cmdline tool: the last commit to the plugin code was somewhen in summer last year.
having said that, there *is* a v0.1 in the repository, and this tag already contains the last change to the deken-plugin. the problem we are facing is, that there there have been changes in the pure-data repository, not reflected in the deken repository.
IOhannes
On 2016-03-22 21:18, IOhannes m zmölnig wrote:
- there is a separate "pd-deployment" branch in the deken repository,
where only "ready to be included" versions of the plugin are found. it's always safe to include the latest version of this branch into Pd.
ok, i've implemented that now. starting with today, there is a branch [pd-deployment], which can safely be used to import the "deken-plugin.tcl" into Pd-vanilla.
it is currently in total sync with the plugin version as shipped with Pd (the only difference is that i used a *comment* to disable one specific line instead of just deleting it)
so in the future, just use the "pd-deployment" task whenver you feel like updating the built-in deken.
fgamsdr IOhannes
[pd-deployment] https://github.com/pure-data/deken/tree/pd-deployment
-
Dan Wilcox -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Miller Puckette