From: "Douglas Anderson" <douglasjanderson@gmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] search functionality in emerge
Date: Sun, 23 Nov 2008 23:56:20 +0900 [thread overview]
Message-ID: <4511e6e80811230656w528284b0r5df94b32aca55175@mail.gmail.com> (raw)
In-Reply-To: <1227450820.27501.0.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 3400 bytes --]
Emma,
It would be great it you could speed search up a bit!
As these other guys have pointed out, we do have some indexing tools in
Gentoo already. Most users don't understand why that kind of functionality
isn't built directly into Portage, but IIRC it has something to do with the
fact that these fast search indexes aren't able to be written to by more
than one process at the same time, so for example if you had two emerges
finishing at the same time, Portage's current flat hash file can handle
that, but the faster db-based indexes can't.
Anyways, that's the way I, as a curious user, understood the problem.
You might be interested in reading this, very old forum thread about a
previous attempt:
http://forums.gentoo.org/viewtopic-t-261580-postdays-0-postorder-asc-start-0.html
On Sun, Nov 23, 2008 at 11:33 PM, Pacho Ramos <
pacho@condmat1.ciencias.uniovi.es> wrote:
> El dom, 23-11-2008 a las 16:01 +0200, tvali escribió:
> > Try esearch.
> >
> > emerge esearch
> > esearch ...
> >
> > 2008/11/23 Emma Strubell <emma.strubell@gmail.com>
> > Hi everyone. My name is Emma, and I am completely new to this
> > list. I've been using Gentoo since 2004, including Portage of
> > course, and before I say anything else I'd like to say thanks
> > to everyone for such a kickass package management system!!
> >
> > Anyway, for my final project in my Data Structures &
> > Algorithms class this semester, I would like to modify the
> > search functionality in emerge. Something I've always noticed
> > about 'emerge -s' or '-S' is that, in general, it takes a very
> > long time to perform the searches. (Although, lately it does
> > seem to be running faster, specifically on my laptop as
> > opposed to my desktop. Strangely, though, it seems that when I
> > do a simple 'emerge -av whatever' on my laptop it takes a very
> > long time for emerge to find the package and/or determine the
> > dependecies - whatever it's doing behind that spinner. I can
> > definitely go into more detail about this if anyone's
> > interested. It's really been puzzling me!) So, as my final
> > project I've proposed to improve the time it takes to perform
> > a search using emerge. My professor suggested that I look into
> > implementing indexing.
> >
> > However, I've started looking at the code, and I must admit
> > I'm pretty overwhelmed! I don't know where to start. I was
> > wondering if anyone on here could give me a quick overview of
> > how the search function currently works, an idea as to what
> > could be modified or implemented in order to improve the
> > running time of this code, or any tip really as to where I
> > should start or what I should start looking at. I'd really
> > appreciate any help or advice!!
> >
> > Thanks a lot, and keep on making my Debian-using professor
> > jealous :]
> > Emma
> >
> >
> >
> > --
> > tvali
> >
> > Kuskilt foorumist: http://www.cooltests.com - kui inglise keelt oskad.
> > Muide, üle 120 oled väga tark, üle 140 oled geenius, mingi 170 oled ju
> > mingi täica pea nagu prügikast...
>
> I use eix:
> emerge eix
>
> ;-)
>
>
>
[-- Attachment #2: Type: text/html, Size: 4891 bytes --]
next prev parent reply other threads:[~2008-11-23 14:56 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 12:17 [gentoo-portage-dev] search functionality in emerge Emma Strubell
2008-11-23 14:01 ` tvali
2008-11-23 14:33 ` Pacho Ramos
2008-11-23 14:43 ` Emma Strubell
2008-11-23 16:56 ` Lucian Poston
2008-11-23 18:49 ` Emma Strubell
2008-11-23 20:00 ` tvali
2008-11-23 21:20 ` Mike Auty
2008-11-23 21:59 ` René 'Necoro' Neumann
2008-11-24 0:53 ` tvali
2008-11-24 9:34 ` René 'Necoro' Neumann
2008-11-24 9:48 ` Fabian Groffen
2008-11-24 14:30 ` tvali
2008-11-24 15:14 ` tvali
2008-11-24 15:15 ` René 'Necoro' Neumann
2008-11-24 15:18 ` tvali
2008-11-24 17:15 ` tvali
2008-11-30 23:42 ` Emma Strubell
2008-12-01 7:34 ` [gentoo-portage-dev] " Duncan
2008-12-01 10:40 ` Emma Strubell
2008-12-01 17:52 ` Zac Medico
2008-12-01 21:25 ` Emma Strubell
2008-12-01 21:52 ` Tambet
2008-12-01 22:08 ` Emma Strubell
2008-12-01 22:17 ` René 'Necoro' Neumann
2008-12-01 22:47 ` Emma Strubell
2008-12-02 0:20 ` Tambet
2008-12-02 2:23 ` Emma Strubell
2008-12-02 10:21 ` Alec Warner
2008-12-02 12:42 ` Tambet
2008-12-02 13:51 ` Tambet
2008-12-02 19:54 ` Alec Warner
2008-12-02 21:47 ` Tambet
2008-12-02 17:42 ` Tambet
2008-11-23 14:56 ` Douglas Anderson [this message]
2008-11-24 3:12 ` [gentoo-portage-dev] " Marius Mauch
2008-11-24 5:01 ` devsk
2008-11-24 6:25 ` Marius Mauch
2008-11-24 6:47 ` [gentoo-portage-dev] " Duncan
2009-02-12 19:16 ` [gentoo-portage-dev] " René 'Necoro' Neumann
[not found] ` <5a8c638a0902121258s7402d9d7l1ad2b9a8ecf9820d@mail.gmail.com>
2009-02-12 21:01 ` Fwd: " Emma Strubell
2009-02-12 21:05 ` Mike Auty
2009-02-12 21:14 ` Emma Strubell
2009-02-13 13:37 ` Marijn Schouten (hkBst)
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=4511e6e80811230656w528284b0r5df94b32aca55175@mail.gmail.com \
--to=douglasjanderson@gmail.com \
--cc=gentoo-portage-dev@lists.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