Gentoo Archives: gentoo-dev

From: Eric Sammer <eric@××××××××××××.com>
To: "gentoo-dev@g.o" <gentoo-dev@g.o>
Cc: Mark Bainter <mark-gt@×××××.org>, Julien Herfurth <jherfurth@××××××.com>
Subject: Re: [gentoo-dev] maybe it is time to put portage queries into a database.
Date: Fri, 27 Jun 2003 06:46:03
In Reply to: Re: [gentoo-dev] maybe it is time to put portage queries into a database. by Mark Bainter
1 Someone stated:
2 >I would say options, tools and the ability to do this sorta stuff should
3 >be optional. I don't wan't to have to run mysql on my laptop however
4 >having portage db in a dbfile would be handy. On the other hand i run 8
5 >machines in my house on Gentoo, and having each machines info and db's
6 >in my mysql server here would be a great boon ( already using local
7 >syncing and nfs mounted dist dirs)
9 Daring to broach the "enterprise" related issues, I would think that
10 this would be one of those things that makes deploying and managing a
11 medium network (>= 500 servers) difficult. To be the chameleon of an OS
12 the average */Linux distro needs to be (netapp, workstation, kiosk,
13 "normal" server, cluster node, etc.) these (hold nose here) "enterprise"
14 features should be implemented in such a way as to easily switch between
15 these applications (of usage).
17 Good example of quick changes: nsswitch as it relates to host info (many
18 options, simple to change between).
20 Bad example: switching file system types (many options, but not "flick
21 of switch" easy to change).
23 Maybe, as an option, moving to a directory service (openldap, et al) for
24 portage naming and access should be considered. Tools similiar to
25 Apple/NeXTSTEP/OpenSTEP 'niload, nicl, nidump' could be used to switch
26 between and migrate easily (or at least more so).
28 Pros:
29 1. extensible
30 2. distributed
31 3. access bindings for most common languages (python, perl, c, c++,
32 etc.) which avoid that particular hot-button.
33 4. easy to replicate (see #1 + #2)
34 5. opens the option of moving other system services easily into the same
35 system (passwd, groups, hosts, email, etc.)
37 Cons:
38 1. can be complex for newbies (overcome with nice tools like
39 mirrorselect, ufed, emerge, et al)
40 2. dependencies (see #3 below)
41 3. potential bloat (arguable and should be considered in relation to the
42 "chameleon" introductory and migration paragraph).
44 The virt host email howto could give the user another option to drop
45 mysql for the directory service thus achieving even more use and sharing
46 of resources. This also opens the company wide enterprise directory (as
47 in addressbook) issue making Gentoo that much more appealing to such
48 entities.
50 Of course, this is something that has probably been kicked around. In
51 this instance, the option of making Gentoo more accessible to corporate
52 and other (hold nose) "enterprise" environments is available.
54 I've worked on many similar ideas and systems in the past and would love
55 to work on something like this for Gentoo.
57 (sorry if this is an old suggestion)
59 Regards...
61 --
62 Eric Sammer
63 eric@××××××××××××.com
67 --
68 gentoo-dev@g.o mailing list