1 |
One interesting application I can think of using a database backend is |
2 |
for making a "portage server" serving portage ebuilds and recording the |
3 |
cache information (as in what is installed with what USE flags) for |
4 |
every single client machine having an "account" on the db. So in effect |
5 |
you would have all your machines without any portage-related files apart |
6 |
from the "emergedb" command and accessory tools. It could be usefull for |
7 |
anyone who needs to deploy a lot of differently configured Gentoo |
8 |
machines really fast. It could also be usefull for administration of |
9 |
production Gentoo machines freeing them of have any "portage bloat" |
10 |
(bloat not in the bad sense, I love portage ;-) (here you would have the |
11 |
machines connect to your central portage server. Very interesting even |
12 |
though it is of limited use to many people. |
13 |
|
14 |
On Fri, 2003-02-07 at 18:34, Yannick Koehler wrote: |
15 |
> For the fun of it, I created a little tool very custom and untested that will |
16 |
> read the the cache files of gentoo and generate on the stdout a valid xml |
17 |
> file. |
18 |
> |
19 |
> Now the schema/dtd has been created without any thinking. This may or not |
20 |
> open the door to people to experiment with a gentoo equivalent database. |
21 |
|
22 |
... |
23 |
|
24 |
> Discussion with carspaski reveal thought that the use of the database will |
25 |
> actually not speed up emerge. Because emerge loads the cache inside an |
26 |
> internal memory database and python allow him to leave that in memory in |
27 |
> between runs making it very fast and efficient as only the require entry of |
28 |
> the database gets loaded instead of the whole database. |
29 |
> |
30 |
> Some benefit I see from the xml db is for side-tools, for example search |
31 |
> description of ebuilds is faster when using xml db as it is a single file and |
32 |
> software only look for string that start with <description>. One can use |
33 |
> grep/regexp to do such query or built an xml capable application. |
34 |
-- |
35 |
Vano D <gentoo-dev@××××××××××××××××.com> |
36 |
|
37 |
|
38 |
-- |
39 |
gentoo-dev@g.o mailing list |