From: "Sebastian Werner" <sebastian@werner-productions.de>
To: <gentoo-dev@gentoo.org>
Subject: AW: AW: [gentoo-dev] USE database?
Date: Mon, 3 Dec 2001 11:02:24 +0100 [thread overview]
Message-ID: <000101c17be1$a0546cb0$6400a8c0@server> (raw)
In-Reply-To: <1007370808.593.0.camel@inspiron.theleaf.office>
GConf for example don't depend on so many libs. I think the only not
system-lib is glib. But this lib is used also by env-update. So no big
problem. Good, the rescue Problem I agree. But it is much faster. Really
cool could it be to store all settings from /etc in binary files. But
that is not your way and not very fsh-compatible - I know. But it could
be a general idea. I don't like to have 100 files which don't follow the
same style. This is not very user-friendly.
Some other idea is to use the sheme of ksyscoca (like KDE-2.2). It reads
text files and builds a binary cache.
Sebastian
-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@gentoo.org [mailto:gentoo-dev-admin@gentoo.org] Im
Auftrag von Geert Bevin
Gesendet: Montag, 3. Dezember 2001 10:13
An: gentoo-dev@gentoo.org
Betreff: Re: AW: [gentoo-dev] USE database?
Hi,
the idea of a binary registry is not the path to follow imho. All system
critical settings and files should depend on as little libraries as
possible and be editable directly. This is very important in case of
system rescue. Putting these settings inside a database of some sort
really removes much of the needed flexibility and creates a magical
black box called 'system configuration' that no-one really knows and
that pretty soon can only be done through dedicate tools ... very bad.
Geert.
On Mon, 2001-12-03 at 08:41, Sebastian Werner wrote:
> Hey,
>
> I like your idea. I have the same problems with the many variables I
> could set. Some other idea I think could be good is to store the data
> with gconf or something else (a binary registry - like windows but
> better).
>
> Sebastian Werner
--
Geert Bevin
the Leaf sprl/bvba
"Use what you need" Pierre Theunisstraat 1/47
http://www.theleaf.be 1030 Brussels
gbevin@theleaf.be Tel & Fax +32 2 241 19 98
_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-12-03 10:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 1:06 [gentoo-dev] USE database? Zach Forrest
2001-12-03 7:41 ` AW: " Sebastian Werner
2001-12-03 9:13 ` Geert Bevin
2001-12-03 10:02 ` Sebastian Werner [this message]
2001-12-03 10:12 ` AW: " Geert Bevin
2001-12-03 11:05 ` AW: " Sebastian Werner
2001-12-03 11:05 ` Geert Bevin
2001-12-03 11:26 ` AW: " Sebastian Werner
2001-12-03 11:32 ` [gentoo-dev] New ideas, USE database, sandbox & more Vitaly Kushneriuk
2001-12-03 11:48 ` Geert Bevin
2001-12-03 12:55 ` Vitaly Kushneriuk
2001-12-03 14:01 ` Joshua Pierre
2001-12-03 16:06 ` Vitaly Kushneriuk
2001-12-03 16:28 ` Daniel Robbins
2001-12-03 18:00 ` Vitaly Kushneriuk
2001-12-03 16:48 ` [gentoo-dev] USE database? Daniel Robbins
2001-12-06 6:01 ` Mikael Hallendal
2001-12-06 18:12 ` Zach Forrest
2001-12-06 20:38 ` Mikael Hallendal
2001-12-06 22:33 ` Zach Forrest
2001-12-06 23:40 ` Daniel Robbins
2001-12-06 23:52 ` Zach Forrest
2001-12-07 19:28 ` Sebastian Werner
2001-12-07 21:39 ` Daniel Robbins
2001-12-07 21:43 ` Geert Bevin
2001-12-08 1:44 ` Mikael Hallendal
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='000101c17be1$a0546cb0$6400a8c0@server' \
--to=sebastian@werner-productions.de \
--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