From owner-freebsd-ports@FreeBSD.ORG Wed Nov 9 14:28:20 2005 Return-Path: X-Original-To: ports@freebsd.org 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 0E91816A41F; Wed, 9 Nov 2005 14:28:20 +0000 (GMT) (envelope-from tobez@tobez.org) Received: from heechee.tobez.org (heechee.tobez.org [217.157.39.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF69843D53; Wed, 9 Nov 2005 14:28:18 +0000 (GMT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 76314125451; Wed, 9 Nov 2005 15:28:17 +0100 (CET) Date: Wed, 9 Nov 2005 15:28:17 +0100 From: Anton Berezin To: Lars Thegler , Alex Dupre , ports@freebsd.org Message-ID: <20051109142817.GG22596@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Lars Thegler , Alex Dupre , ports@freebsd.org References: <20051107154634.GA40923@heechee.tobez.org> <43704ACA.1070708@FreeBSD.org> <437062D6.6050001@FreeBSD.org> <20051109045413.GA64842@holestein.holy.cow> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051109045413.GA64842@holestein.holy.cow> User-Agent: Mutt/1.4.2.1i X-Powered-By: FreeBSD http://www.freebsd.org/ Cc: Subject: Re: Request for comments: port-tags X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 14:28:20 -0000 On Tue, Nov 08, 2005 at 11:54:13PM -0500, Parv wrote: > in message <437062D6.6050001@FreeBSD.org>, > wrote Lars Thegler thusly... > > > > Alex Dupre wrote: > > >like it very much. One thing we can add to enhance the tag > > >classification is to add an optional PORTTAGS variable where we can > > >define additional tags (not present in CATEGORY and COMMENT) for the > > >port, so that "Maildir" could be for example associated with > > >mail/dovecot. This will require additional work for maintainers, but I > > >think it'll highly improve the searches. > > > > I suspect most (if not all) tag addition could be done within COMMENT > > itself. For people browsing the portstree through other means, say, > > FreshPorts, improving COMMENT makes very good sense, IMHO. > > When i read COMMENT, i want to know the purpose of the port. > Currently, in most cases i have to read pkg-descr to get a better > understanding (as COMMENT is just filler). (Yes, i know that only > thing that can improve the current situation would be to file PRs to > better define COMMENT.) > > If keywords start filling COMMENT, i think purpose of COMMENT will > fail. Then again, rereading what i wrote in the above paragraph, > COMMENT will server a fruitful purpose finally by containing > keywords (albeit under a indirectly related variable name). I will support a TAGS field; what I cannot decide at this moment, is whether to ignore COMMENT and pkg-descr (support for which I will add shortly) when TAGS is present, or use TAGS as an additional tag source only. \Anton. -- An undefined problem has an infinite number of solutions. -- Robert A. Humphrey