On 18 April 2013 11:53, Martin Jansa <[email protected]> wrote: > On Thu, Apr 18, 2013 at 10:51:21AM +0100, Paul Barker wrote: >> 1) vim has new patch releases very often so if I stick with a fixed >> version we'll fall behind quickly. However the default branch might >> become vim-7.4 at some point in the future but I'm not sure we want to >> move to that automatically. There isn't even a vim-7.4 development >> branch in the upstream repository so that may be a long while away. Do >> you have any advice on whether I should specify a fixed version or use >> AUTOREV? It could also be possible to include both a vim_7.3.905.bb >> file and a vim_hg.bb file. > > No AUTOREV in meta-oe, but it's fine to add both > vim_7.3.905.bb and vim_hg.bb if hg versions have negative > DEFAULT_PREFERENCE and SRCREV that you can confirm is working (you can change > it to AUTOREV later in your local.conf if you want). >
Pretty much every commit to the default branch of vim is released as a new version (hence .905) so I'll just stick with the single vim_7.3.905.bb file. >> 3) There's a vimrc file kept along with the recipe for vim, I can't >> see much useful in the git history of this file. There's also a >> vimrc_example.vim file in the runtime files distributed with vim that >> will keep up-to-date with any changes to syntax or features, should we >> move to using this? > > You mean to use vimrc_example.vim from vim archive instead of our local > vimrc copy? Sounds good too. > Yes that's right. I'll split this change out into a separate patch. -- Paul Barker Email: [email protected] http://www.paulbarker.me.uk _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
