From owner-freebsd-ports@FreeBSD.ORG Mon Nov 22 04:04:21 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01EBA16A4D0; Mon, 22 Nov 2004 04:04:21 +0000 (GMT) Received: from lakermmtao06.cox.net (lakermmtao06.cox.net [68.230.240.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4987543D1F; Mon, 22 Nov 2004 04:04:20 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by lakermmtao06.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041122040417.KHY5535.lakermmtao06.cox.net@mezz.mezzweb.com>; Sun, 21 Nov 2004 23:04:17 -0500 To: "Jose M Rodriguez" References: <41A01DF9.9090607@sc.rr.com> <200411220327.31085.freebsd@redesjm.local> <200411220439.31998.freebsd@redesjm.local> Message-ID: Date: Sun, 21 Nov 2004 22:05:03 -0600 From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <200411220439.31998.freebsd@redesjm.local> User-Agent: Opera M2/7.54 (Linux, build 751) cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: vim-lite-6.3.16 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 04:04:21 -0000 On Mon, 22 Nov 2004 04:39:31 +0100, Jose M Rodriguez wrote: > El Lunes, 22 de Noviembre de 2004 04:06, Jeremy Messenger escribió: >> On Mon, 22 Nov 2004 03:27:30 +0100, Jose M Rodriguez >> >> 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. > > Not. Is somewhat allready done: > from editors/vim/Makefile: > > .if defined(PACKAGE_BUILDING) && !defined(LITE) > WITH_TCL= yes > WITH_PERL= yes > WITH_PYTHON= yes > WITH_CSCOPE= yes > .endif > >> >> > 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 >> ========================================= >> >> It will work with and without portupgrade. I use above rather than >> use pkgtools.conf. >> >> Cheers, >> Mezz >> > > And ... How can I make the package building cluster use this? Uh oh, package, sorry I wasn't pay attention to it... Nevermind my reply then, but if your own package cluster then you can. > What I really don't like of the actual vim port is that default port > build is very different from package build. > > I can recall this as the most common package build on Unix (al last, on > Linux). > > And what we really must define is what packages are to be build. Now, > we build: > - a gtk vim (with tcl, perl, python and cscope) > - a vim-lite > > I think that we must build (as packages, no ports clues). > > - a Non-X11, perl and cscoped enabled vim from editor/vim (most used) > - a vim-lite > - a vim-gtk2 vim from editors/vim-gtk2 > - a X11 enabled (gtk?) vim from other slave port? > - an 'all enabled' devel-vim from other port? > > ALso, I think that gtk packages must have i18n enabled by default. > > -- > josemi -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org