| 1 |
>>>>> "Ingo" == Ingo Krabbe <i.krabbe@×××××.net> writes: |
| 2 |
|
| 3 |
Ingo> On Sat, Feb 01, 2003 at 07:16:44PM +1000, Rendhalver [Peter Brown] wrote: |
| 4 |
>> ah ok so you want to put the actual portage tree into a database yes? |
| 5 |
|
| 6 |
Ingo> nope, I think it would be much nicer to portage to create a mirror |
| 7 |
Ingo> image of the portage tree in a database, together with all textual |
| 8 |
Ingo> information available. I want to leave the portage as it is for |
| 9 |
Ingo> installing and updating packages but I want to be able to get events |
| 10 |
Ingo> from portage when new packages arrive (rsync), are installed (emerge) |
| 11 |
Ingo> or uninstalled (unmerge) or updated (emerge -u), so I can keep track of |
| 12 |
Ingo> it. |
| 13 |
|
| 14 |
sounds like a fun and useful project |
| 15 |
|
| 16 |
Ingo> Of course it would be a solution to manage everything in a database, hmm |
| 17 |
Ingo> it is a tree you know, a big tree in recent times, so it should be a |
| 18 |
Ingo> database object. But the evolution of portage was filesystem oriented, |
| 19 |
Ingo> which is understandable for portability, stability and transparency. At |
| 20 |
Ingo> least the filesystem is a database too, a slow one though, but fast |
| 21 |
Ingo> enough for the installation purposes, measured against the compilation |
| 22 |
Ingo> and download times. |
| 23 |
|
| 24 |
Ingo> I often bothered about the problem of searching a package by keyword or |
| 25 |
Ingo> package name (emerge -s foo) and (emerge -S foo), when I just want to |
| 26 |
Ingo> get a quick overview about a topic or want to look up this new package I |
| 27 |
Ingo> just heard of in this newgroup yesterday. |
| 28 |
|
| 29 |
yeah i know what you mean there |
| 30 |
|
| 31 |
you would have to make it so the database can be easily updated from |
| 32 |
the output of a emerge rsync (or a cvs update for us developer types) |
| 33 |
or do some kind of check on the portage tree for modifications to ebuilds |
| 34 |
|
| 35 |
Ingo> This operation takes much too long for my taste and thats what I like to |
| 36 |
Ingo> keep in a database. I know there are textual database systems like |
| 37 |
Ingo> htref, but I don't understand their installation and configuration |
| 38 |
Ingo> syntax. Hmm, I'm a C Programmer you know, it is much easier to me to |
| 39 |
Ingo> put everything in a Berkeley DB put a job in the background and fire |
| 40 |
Ingo> some events or raise some signals. |
| 41 |
|
| 42 |
i know what you mean there :) |
| 43 |
i would use something that can talk to multiple database backends so |
| 44 |
the user has a choice in database to use |
| 45 |
|
| 46 |
maybe you could use libgda/libgnomedb/mergeant for this ?? |
| 47 |
they can talk to lots of databases and the list is growing as well |
| 48 |
last i looked there was an LDAP backend for libgda |
| 49 |
|
| 50 |
-- |
| 51 |
XEmacs Advocate | Do not try the patience of Wizards, |
| 52 |
Gentoo Developer | for they are subtle and quick to anger. |
| 53 |
Perl Hacker | - Elric (Technomage) , Babylon 5. |
| 54 |
Apache God | <mailto:rendhalver at gentoo.org> <GnuPG KeyID: AE51D190> |
| 55 |
|
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-dev@g.o mailing list |
Archives