Re: Please review icecc

[Iain Hibbert <plunky%rya-online.net@localhost> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 1.0 FORGED_RCVD_HELO Received: contains a forged HELO -0.5 AWL AWL: From: address is in the auto white-list]

On Wed, 9 Mar 2005, David Howland wrote:

> Iain Hibbert wrote:
> > I cant see a useful way to have a dependency on Vim, since it comes in 
> > various flavours (vim, vim-gtk2, vim-kde, vim-motif, etc..) and they are 
> > mutually exclusive. 
>
> I would also like to know the solution to this problem, if anyone has one.  I 
> have a package that depends on gvim, and at the moment I just have it 
> depending on vim-gtk2, because that is what I use, but a more general 
> solution would be better.

I have suggested to the maintainer of vim that he splits out the 
VIM_VERSION information into a "version.mk" file in the vim-share 
directory.  That way, we can do something like:

.include "../../editors/vim-share/version.mk"
.if exists(${PREFIX}/bin/gvim)
DEPENDS+=               
vim-share-${VIM_VERSION}.${VIM_PATCHLEVEL}:../../editors/vim-share
.else
DEPENDS+=               
vim-gtk2-${VIM_VERSION}.${VIM_PATCHLEVEL}:../../editors/vim-gtk2
.endif

in the Makefile, which makes pkglint give warnings (because DEPENDS should 
appear earlier) but I dont see another way.

regards,
iain


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
pkgsrc-wip-review mailing list
pkgsrc-wip-review%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-review