On 2014/07/17 23:39, Edd Barrett wrote:
> Hi Stuart,
>
> Thanks for the input. All sounds reasonable to me.
>
> On Thu, Jul 17, 2014 at 12:04:21PM +0100, Stuart Henderson wrote:
> > On 2014/07/17 11:17, Edd Barrett wrote:
> > > On Sat, Jun 28, 2014 at 01:49:04PM +0100, Edd Barrett wrote:
> > I don't have the original mail with the attachment any more and no
> > time to dig list archives.
>
> Here we are:
> https://github.com/jasperla/openbsd-wip/blob/master/editors/vim-command-t/Makefile#L53
>
> --
> Best Regards
> Edd Barrett
>
> http://www.theunixzoo.co.uk
>
# Convoluted way to extract a vimball in an automated fashion.
do-extract:
HOME=${WRKDIR} ${LOCALBASE}/bin/vim \
--cmd ":set nocp" \
--cmd ":runtime vimballPlugin.vim" \
-c ":silent so %" \
-c ":qa" \
${DISTDIR}/${DISTNAME}${EXTRACT_SUFX}
yowzers!
Actually that is a bit of a pain for people who want to extract ports
source.
Can you turn it into a tar instead? No problem hosting it. I would
modify the "do-extract" target and have it create a tar for you
(maintainer "convenience" target, like "tar" in vim itself, or the
targets in geoip and arp-scan).
# XXX We remove the helptags because the file is owned by editors/vim.
# If we were to change the file we would screw up checksums.
# Perhaps remove the helptags from the vim ports and generate them
# at install time using an @exec?
it might be worth investigating this option, though what you have
now is probably good enough for now.
