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