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?)