From: Thomas Flavel <thomasfl@cogs.susx.ac.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Tom
Date: Thu Jan 25 09:11:01 2001 [thread overview]
Message-ID: <20010125161057.A26673@tsuny.ctn.cogs.susx.ac.uk> (raw)
In-Reply-To: <3A702404.789AA202@gottinger.de>; from 320095285153-0001@t-online.de on Thu, Jan 25, 2001 at 02:03:01PM +0100
On Thu, Jan 25, 2001 at 02:03:01PM +0100, Achim Gottinger wrote:
> > >
> > > > From what I can see it has a binary cd version, with the option
> > > > to compile from source (the same thing I was talking about, if I understand them
> > > > correctly). It describes it's package management as closer to FreeBSD than debian.
> > > > It looks to be quite similar to gentoo to me, although not quite as advanced.
> > >
> > > I took a look at the site and think that we need something similar to cfengine
> > > sometimes.
> >
> > That looks like a great idea; I was wondering about something similar for configuring
> > applications; i.e. some way to save a "theme" for the applications I use (e.g. colours
> > for lynx matching the colours for man pages etc if you see what I mean)
>
> You mean the user-specific dor-config-files?
>
Hmmm... I'm just thinking aloud here; I'm not even sure if it's a useful idea, nor am I sure
that I can explain it satisfactorialy :/
Ok, from the users perspective, it would look like this: A default configuration skeleton would
be installed (a default ~/.bashrc etc), as it is currently. The user would then be able to
apply, um, "themes" to their configuration - for example I like the highlight colour to be red,
so I would find myself going through ~/.pinerc, ~/.lynxrc etc making them all look the same...
the same applies to things like prompts, shells, editor of choice, my favorite mail program,
/etc/hosts etc etc.
How could this theming work? I thought perhaps a central data file, containing (bear with my
example please ;) things like $FAVORITE_COLOUR etc - a script could then be run to update the
appropiate rc files.
I'm picturing the data for the skeleton rc files being part of the ebuild package; I guess it
would have to be extracted to some database reminicient of termcap...
I don't think this is particularly urgent; as I said, I'm just thinking aloud. It's just an idea
to let you reconfigure everything to the way you like it... I'm not even sure I have exaplined
it correctly... basically cfengine but extended to allow for changing variables in rc files too
- Tom
next prev parent reply other threads:[~2001-01-25 16:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010124234502.4D5CF51353@cvs.gentoo.org>
2001-01-24 18:29 ` [gentoo-dev] Re: Tom Bryce Porter
2001-01-24 18:53 ` Thomas Flavel
2001-01-25 4:47 ` Achim Gottinger
2001-01-25 5:54 ` Thomas Flavel
2001-01-25 6:05 ` Gabriel
2001-01-25 6:49 ` Achim Gottinger
2001-01-25 9:53 ` drobbins
2001-01-25 10:48 ` [gentoo-dev] Hurd Gabriel
2001-01-25 10:56 ` drobbins
2001-01-25 11:01 ` Gabriel
2001-01-25 11:13 ` [gentoo-dev] Re: Tom Jerry A!
2001-01-25 11:37 ` Gabriel
2001-01-25 11:46 ` Jerry A!
2001-01-25 11:52 ` drobbins
2001-01-25 6:31 ` Achim Gottinger
2001-01-25 9:11 ` Thomas Flavel [this message]
2001-01-25 9:01 ` Bill Anderson
2001-01-25 9:08 ` Bill Anderson
2001-01-25 9:29 ` Achim Gottinger
2001-01-25 9:30 ` Achim Gottinger
2001-01-25 10:24 fruhstuck
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=20010125161057.A26673@tsuny.ctn.cogs.susx.ac.uk \
--to=thomasfl@cogs.susx.ac.uk \
--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