public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] maybe it is time to put portage queries into a database.
Date: Wed, 25 Jun 2003 12:39:28 +0200	[thread overview]
Message-ID: <200306251239.35377.pauldv@gentoo.org> (raw)
In-Reply-To: <20030625004141.5fa0bff9.genone@genone.homeip.net>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1127 bytes --]

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.
>

The problem is the enormous amount of ebuilds we offer. The amount of ebuilds 
is currently: 8553 and the amount of files is: 50435.

Try the following script to make searching faster:
find /usr/portage/ -name "*.ebuild" -exec grep -H DESCRIPTION {} \; \
  |awk -F: '{ sub("(/usr/portage/[^/]*/)","",$1); sub("/.*","",$1); \
  printf("%-20s:%s\n", $1, $2) }'|sort |uniq >~/descriptions

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

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-06-25 10:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 22:00 [gentoo-dev] maybe it is time to put portage queries into a database Tony Clark
2003-06-24 22:16 ` jesse
2003-06-24 22:36   ` Tony Clark
2003-06-25  6:30     ` Sven Vermeulen
2003-06-24 22:52   ` Julien Herfurth
2003-06-24 22:36     ` Henti Smith
2003-06-24 23:04       ` jesse
2003-06-24 22:58         ` Henti Smith
2003-06-24 23:57           ` Brian Jackson
2003-06-25  3:05             ` Tony Clark
2003-06-25  3:37           ` jesse
2003-06-24 23:04     ` Tony Clark
2003-06-27  2:03     ` Mark Bainter
2003-06-27  6:45       ` Eric Sammer
2003-06-27 12:23         ` [gentoo-dev] Directory services (was Re: [gentoo-dev] maybe it is time to put portage queries into a database.) Eric Sammer
2003-06-27 12:58           ` Rigo Ketelings
2003-06-27 14:58             ` Zack Gilburd
2003-06-27 15:21               ` c.wegener
2003-06-27 15:27                 ` Patrick Kursawe
2003-06-27 15:38                   ` Eric Sammer
2003-06-27 15:28               ` Eric Sammer
2003-06-27 15:32                 ` Patrick Kursawe
2003-06-27 15:41                   ` Eric Sammer
2003-06-27 19:38               ` Paul de Vrieze
2003-06-24 22:16 ` [gentoo-dev] maybe it is time to put portage queries into a database Brian Jackson
2003-06-24 22:41   ` Tony Clark
2003-06-24 22:41 ` Marius Mauch
2003-06-24 23:14   ` kl4rk
2003-06-25  2:20     ` jesse
2003-06-25  4:08   ` Matthew Kennedy
2003-06-25 10:39   ` Paul de Vrieze [this message]
2003-06-25 11:01     ` kl4rk
2003-06-25 11:57       ` rob holland
  -- strict thread matches above, loose matches on Subject: below --
2003-06-24 22:33 Anthony Floyd
2003-06-24 23:02 ` Tony Clark
2003-06-25  9:53 ` Henti Smith
2003-06-25  1:21 Tony Clark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200306251239.35377.pauldv@gentoo.org \
    --to=pauldv@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox