From owner-freebsd-ports@FreeBSD.ORG Tue Oct 26 19:40:10 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 DF68316A4CE for ; Tue, 26 Oct 2004 19:40:10 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DCB143D41 for ; Tue, 26 Oct 2004 19:40:10 +0000 (GMT) (envelope-from jeffgaofreebsd@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so217498wri for ; Tue, 26 Oct 2004 12:40:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=sEsd07OBn8aBVq9esVNtGHzVPGP+p5nW6g+tpwq2pkme+4woOG5+mMUKmaGIWq+oXsdeNA5PJH9EMAec9w1HVAgiv6o2cqzsuC51YPx4Mp+GXm6fKjW+AUlLFZqK57HgtUh2IqBGvQkyrebGN7fSHNgtDWYC0XSdgBXx6WadGpk= Received: by 10.38.82.27 with SMTP id f27mr668337rnb; Tue, 26 Oct 2004 12:40:09 -0700 (PDT) Received: by 10.38.74.3 with HTTP; Tue, 26 Oct 2004 12:40:09 -0700 (PDT) Message-ID: <639522fe04102612404109e5e7@mail.gmail.com> Date: Tue, 26 Oct 2004 13:40:09 -0600 From: Jie Gao To: Mike Edenfield In-Reply-To: <4179366C.9010404@kutulu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041022074529.GN10363@k7.mavetju> <41791AF7.2050009@vonostingroup.com><4179366C.9010404@kutulu.org> cc: Benjamin Lutz cc: freebsd-ports@freebsd.org Subject: Re: ports/www is too full X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jie Gao List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 19:40:11 -0000 I agree this. If we have a powerful search utility instead of the simple "make search", it doesn't matter how large the directories are. On Fri, 22 Oct 2004 12:33:48 -0400, Mike Edenfield wrote: > Benjamin Lutz wrote: > > > Reading between the lines, the problem you're having is that the ports > > aren't well enough categorized at the moment. How about borrowing an idea > > from some of the knowledge databases, and using keywords to mark ports? > > Eg, instead of creating a www-server category, the apache port could be > > marked "server www". linux-opera could be market "binary browser client > > linux www" or something like that. > > FreeBSD already has "virtual" categories -- categories that aren't used > to physically sort the ports. For example, devel/tcl84/Makefile has: > CATEGORIES= lang tcl84 > > tcl84 isn't a real folders, but it's listed in a number of port's > $ make search key=tcl84 | grep "Port:" | wc -l > 40 > > One thing I don't see is a way to search or sort by category, but I > admit to not having looking very hard. > > --Mike > > > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >