From owner-freebsd-ports@FreeBSD.ORG Tue Oct 18 15:37:53 2005 Return-Path: X-Original-To: freebsd-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 85F5F16A41F for ; Tue, 18 Oct 2005 15:37:53 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id D805543D48 for ; Tue, 18 Oct 2005 15:37:52 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 5D79C2FFB; Tue, 18 Oct 2005 10:37:52 -0500 (CDT) Date: Tue, 18 Oct 2005 10:37:52 -0500 To: Wes Peters Message-ID: <20051018153752.GB11790@soaustin.net> References: <4350CE50.8080704@ebs.gr> <5739E97B-7EDC-4971-9EA5-01A44688A981@softweyr.com> <43522953.6050700@ebs.gr> <1B8112AF-8C0E-4BA0-8D1C-DA6AD529F327@softweyr.com> <20051017153024.GA23494@arabica.esil.univ-mrs.fr> <20051017212748.GD71766@isis.sigpipe.cz> <790a9fff0510171505i4010cc05yc30f67d459d1a0e4@mail.gmail.com> <20051018010446.GH71766@isis.sigpipe.cz> <20051018011616.GA57969@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Scot Hetzel , freebsd-ports@freebsd.org, Kris Kennaway Subject: Re: [SUGGEST] Reform eclipse and eclipse related ports 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: Tue, 18 Oct 2005 15:37:53 -0000 On Mon, Oct 17, 2005 at 11:39:52PM -0700, Wes Peters wrote: > I'm not pointing this out for my use; I'm pretty adept at finding > stuff in ports. I have a lot of co-workers who are experienced > programmers but not necessarily experience FreeBSD'ers and they often > have trouble finding ports even when they (almost) know the name. That highlights my point that IMHO we need two different functionalities: 'search' and 'browse'. 'make search' is barely adequate for searching. We have nothing at all for browsing (unless you count reading an entire list of ports in hierarchy as 'browsing', which even an old command-line kind of guy like me thinks is crude). IMHO these things are better addressed at the application level, not inside bsd.port.mk itself. See sysutils/portmanager for what I think is an interesting first step towards that direction. That's where I think our work should focus, not on directory structure. mcl