Ken Takata wrote: > Hi Bram and Christian, > > 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote: > > Ken Takata wrote: > > > > > Hi Bram, > > > > > > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote: > > > > I am including the changes to gvim.nsi. I also updated the code to look > > > > for libintl-8.dll, since that one uses the iconv libraray. The one I > > > > used so far was quite old. > > > > > > > > Please let me know if this doesn't work and further changes are needed. > > > > > > I think all the changes needed are fully merged. (except the build > > > scripts) > > > > > > How about this idea? > > > https://groups.google.com/d/msg/vim_dev/dAXpcpHmVw4/i6X-SqP1BAAJ > > > Maybe it's better to use git submodule. > > > If you like this, I will try it on my repository. > > > > I'm not sure what that means... > > > > Building the gvim.exe once per day seems about right. Not sure how to > > set that up. Perhaps some kind of automatic pull on the submodule? > > > > We could just build on every commit, but I've already seen builds fail > > because there are not sufficient resources. > > Okay, I set up another repository: > https://github.com/k-takata/vim-win32-installer > > This includes the vim/vim repository as a submodule. > When a tag is pushed to the vim-win32-installer repository, an appveyor build > starts and built packages are uploaded to the release page: > https://github.com/k-takata/vim-win32-installer/releases > (Not to the release page of vim/vim.)
That looks nice! Redirecting from the Vim doesnload page to here would make most people happy. I think the only hint that's needed is "in case you don't have a preference, download the "_x86.exe" file and run it". Once in a while I can take one of the builds and put it on ftp.vim.org and link to it directly from the download page. This would be the "stable version". It will never be the latest, since it takes a few days to make sure that there are no regressions. > Build history is here: > https://ci.appveyor.com/project/k-takata/vim-win32-installer > > Scripts for appveyor are here: > https://github.com/k-takata/vim-win32-installer/blob/master/appveyor.bat > https://github.com/k-takata/vim-win32-installer/blob/master/appveyor.yml > > And here is a (sample) script for updating this repository: > https://github.com/k-takata/vim-win32-installer/blob/master/scripts/update-repo.sh > > If this script is run once per day, gvim.exe will be built once per day. > Maybe it's better to run on Christian's server. > > How about this? > And how about creating github.com/vim/vim-win32-installer repository? -- How To Keep A Healthy Level Of Insanity: 4. Put your garbage can on your desk and label it "in". /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
