FreeBSD Port: vim-lite-6.3.16

Jeremy Messenger mezz7 at cox.net
Sun Nov 21 19:31:47 PST 2004


On Mon, 22 Nov 2004 14:29:28 +1100, Edwin Groothuis <edwin at mavetju.org>  
wrote:

> On Sun, Nov 21, 2004 at 09:06:40PM -0600, Jeremy Messenger wrote:
>> On Mon, 22 Nov 2004 03:27:30 +0100, Jose M Rodriguez
>> <josemi at freebsd.jazztel.es> wrote:
>>
>> >El Lunes, 22 de Noviembre de 2004 03:00, David O'Brien escribi??:
>> >>On Sun, Nov 21, 2004 at 12:52:19PM -0800, David O'Brien wrote:
>> >>> On Sun, Nov 21, 2004 at 07:41:14PM +0100, Jose M Rodriguez wrote:
>> >>> > El Domingo, 21 de Noviembre de 2004 18:27, David O'Brien
>> >>> > escribi?:
>> >>> >
>> >>> > cp> On Sun, Nov 21, 2004 at 06:06:27AM +0100, Pav Lucistnik wrote:
>> >>> > > > William Allison p??e v so 20. 11. 2004 v 23:47 -0500:
>> >>> > > > > I'm sorry but I can't seem to figure this out and haven't
>> >>> > > > > been able to get help on IRC.
>> >>> > > >
>> >>> > > > [ ... ]
>> >>> > >
>> >>> > > I would more than welcome a patch for a tested vim-gtk (or
>> >>> > > vim-gtk2) slave port[*] that I could review and test.
>> >>> >
>> >>> > I use this locally for weeks
>> >>>
>> >>> This isn't a slave port.  See vim-lite for an example of what I
>> >>> mean. Also your patch un-portlint's the Makefile more than it
>> >>> already is.
>> >>
>> >>Why isn't the following suffient for a GTK slave port?
>> >
>> >I just prefer fix what I really want.
>>
>> It's personal matter, I will not want to have Perl, cscope and etc in  
>> GTK
>> slave port if it creates.
>>
>> >WITH_GTK2=yes
>> >WITH_I18N=yes		# localized menus and messages
>> >WITH_CSCOPE=yes		# cscope support
>> >WITH_PERL=yes		# perl integration
>> >
>> >So this can be build as package even with only BATCH=yes.
>>
>> Solution add this in your make.conf:
>> =========================================
>> .if ${.CURDIR:M*/editors/vim}
>> WITH_GTK2=yes
>> WITH_I18N=yes		# localized menus and messages
>> WITH_CSCOPE=yes		# cscope support
>> WITH_PERL=yes
>> .endif
>> =========================================
>
> Or let the port use OPTIONS and you have a more scalable way of
> configuring these options.

OPTIONS is the last thing that I will want to touch. It doesn't solve  
problem.

Cheers,
Mezz

> Edwin


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org


More information about the freebsd-ports mailing list