From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22377 invoked by uid 1002); 25 Jun 2003 11:01:38 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 20531 invoked from network); 25 Jun 2003 11:01:38 -0000 Date: Wed, 25 Jun 2003 13:01:36 +0200 From: kl4rk To: gentoo-dev@gentoo.org Message-Id: <20030625130136.2baf835a.kl4rkmail@jazzfree.com> In-Reply-To: <200306251239.35377.pauldv@gentoo.org> References: <200306250000.00937.tclark@telia.com> <20030625004141.5fa0bff9.genone@genone.homeip.net> <200306251239.35377.pauldv@gentoo.org> X-Mailer: Sylpheed version 0.9.0 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] maybe it is time to put portage queries into a database. X-Archives-Salt: ea7de7f2-b06f-4447-b506-225a8fe94c35 X-Archives-Hash: 90da0ca91054d55a5350e687dd3b7e63 On Wed, 25 Jun 2003 12:39:28 +0200 Paul de Vrieze wrote: > On Wednesday 25 June 2003 00:41, Marius Mauch wrote: > > > > BTW, I also noted the slowness of the search function, especially when > > searching in descriptions, my worst measured result was 25 minutes! Most > > likely caused by a serious lack of ram, but half an hour just to find a > > package is really annoying. > > > > This will make a nice file with all descriptions for all packages, filtered > for duplicates. Just use grep on this file instead of emerge -S and you can > find the package. If you put the creation of this file in crontab, you have > yourself a fast and flexible solution, with only 4726 lines of descriptions. > > Paul Maybe instead of having a description in the ebuild itself, there could be a single file per package cointaining the description (and maybe other stuff). That'd make searches faster. There's no point in having the description in the ebuild as it is something static that won't probably change between versions. Having it in the ebuild means (not 100% sure here) parsing the entire ebuild just to read the descr, which is too much work for a single line of text. If the number of packages continues to grow that'll become a bigger and bigger pain. Having a sepparate file for descriptions might allow one day easlily adding bigger descriptions (for the user not to need visiting the package's homepage). Josep -- gentoo-dev@gentoo.org mailing list