On 2014/07/17 11:17, Edd Barrett wrote: > On Sat, Jun 28, 2014 at 01:49:04PM +0100, Edd Barrett wrote: > > However, the port is quite unusual and whilst I have managed to mostly get > > this into shape, there are still some outstanding issues which I am at a > > loss on: > > > > * MODRUBY_REV needs to kept in sync with editors/vim. Is there a way > > to do this without creating a vim.port.mk (seems overkill). > > * Similarly the vim runtime path is hardcoded.
You can add a short (no more than 1 line) comment to vim's Makefile, immediately before VERSION, reminding that this needs a bump. As a failsafe for the runtime path, you could set a build dependency on vim->=7.4,<7.5 though this doesn't help MODRUBY_REV. > > * Vim dependency is too strong. Is there a way to express "any vim > > package including the ruby FLAVOR?" vim-*-ruby:editors/vim,no_x11,ruby first part "vim-*-ruby" is used to match; if not present then the user will have a choice but no_x11,ruby will be the default. If the user has an existing flavour without ruby, they get to fix that themselves. > > * we can't install the helptags for the plugin since editors/vim > > has the tags in it's packing list already. See the XXX in the > > Makefile for one possible workaround. I don't have the original mail with the attachment any more and no time to dig list archives. > Anyone had any thoughts on the above? > > -- > Best Regards > Edd Barrett > > http://www.theunixzoo.co.uk >
