public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ingo Krabbe <i.krabbe@dokom.net>
To: Gentoo Developer <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] portage database management
Date: Sat, 1 Feb 2003 10:25:43 +0100	[thread overview]
Message-ID: <20030201092543.GA10659@dokom.net> (raw)
In-Reply-To: <864r7o9x8j.fsf@ulthwe.dyndns.org>

On Sat, Feb 01, 2003 at 07:16:44PM +1000, Rendhalver [Peter Brown] wrote:
> ah ok so you want to put the actual portage tree into a database yes?

nope, I think it would be much nicer to portage to create a mirror
image of the portage tree in a database, together with all textual
information available.  I want to leave the portage as it is for
installing and updating packages but I want to be able to get events
from portage when new packages arrive (rsync), are installed (emerge)
or uninstalled (unmerge) or updated (emerge -u), so I can keep track of
it.

Of course it would be a solution to manage everything in a database, hmm
it is a tree you know, a big tree in recent times, so it should be a
database object.  But the evolution of portage was filesystem oriented,
which is understandable for portability, stability and transparency.  At
least the filesystem is a database too, a slow one though, but fast
enough for the installation purposes, measured against the compilation
and download times.

I often bothered about the problem of searching a package by keyword or
package name (emerge -s foo) and (emerge -S foo), when I just want to
get a quick overview about a topic or want to look up this new package I
just heard of in this newgroup yesterday.

This operation takes much too long for my taste and thats what I like to
keep in a database.  I know there are textual database systems like
htref, but I don't understand their installation and configuration
syntax.  Hmm, I'm a C Programmer you know, it is much easier to me to
put everything in a Berkeley DB put a job in the background and fire
some events or raise some signals.

BYE INGO

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-02-01  9:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 19:38 [gentoo-dev] portage database management Ingo Krabbe
2003-02-01  8:37 ` Rendhalver [Peter Brown]
2003-02-01  8:35   ` Ingo Krabbe
2003-02-01  9:16     ` Rendhalver [Peter Brown]
2003-02-01  9:25       ` Ingo Krabbe [this message]
2003-02-01 10:17         ` Rendhalver [Peter Brown]
2003-02-01 11:06           ` John Nilsson
2003-02-01 12:35             ` Ingo Krabbe
2003-02-01 15:34             ` Dylan Carlson
2003-02-02  3:29               ` Mark Constable
2003-02-02  5:44                 ` Jim Nutt
2003-02-01 15:34         ` Dylan Carlson
2003-02-01 16:02           ` Ingo Krabbe
2003-02-03  9:19 ` [gentoo-dev] " Christian Plessl
2003-02-03 20:45   ` Marko Mikulicic
  -- strict thread matches above, loose matches on Subject: below --
2003-02-04  7:59 [gentoo-dev] " Brian Friday
2003-02-06  9:41 ` Jared H. Hudson
2003-02-06 19:37   ` Alain Penders
2003-02-06 20:15     ` Riyad Kalla
2003-02-06 22:20     ` Brian Friday
2003-02-06 22:30       ` Riyad Kalla
2003-02-07  3:37         ` Mario Witt
2003-02-07  6:53         ` Matt Tucker

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=20030201092543.GA10659@dokom.net \
    --to=i.krabbe@dokom.net \
    --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