nengo-1.4
nengo-1.4 copied to clipboard
nengo
Auto-update mechanism
This is more of a wishlist item than something for the foreseeable future, but it would be nice to implement an auto-update mechanism, so that people who install Nengo from the website can get updates without having to re-download nengo-latest.zip and unzipping it to the directory. If we control the update mechanism, we can also make sure updates clean up things that we change between versions.
This would work wonderfully if you have releases staged out to Maven. We could actually use Maven for the auto-update process, simply by having it download your artifacts. If you're interested, the first step would be to create a "launcher" project which is little more than a thin shim for maven, which could then handle the rest of the effort required to maintain an up-to-date primary project and any relevant dependencies.
What do you think?
Would that require having all users have maven installed on their computers? Or would we make Maven a dependency of Nengo? I'm not sure if it's worth such a big dependency just for auto-updating, but perhaps!
I think the best idea on Windows would be to write a stand-alone launcher that has an embedded instance of Maven, freeing the user from having to install it. Ideally, the launcher would be the only thing the user actually installed. For Linux platforms, we can make maven a dependency and invoke the one on the platform.
From: Trevor Bekolay Sent: Sunday, December 23, 2012 2:40 PM To: ctn-waterloo/nengo Cc: Jason Sanchez Subject: Re: [nengo] Auto-update mechanism (#172)
Would that require having all users have maven installed on their computers? Or would we make Maven a dependency of Nengo? I'm not sure if it's worth such a big dependency just for auto-updating, but perhaps!
— Reply to this email directly or view it on GitHub.