public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Huddleston <eradicator@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: toolchain@gentoo.org
Subject: [gentoo-dev] Re: gcc-config 2.0 development
Date: Tue, 09 Aug 2005 15:12:48 -0700	[thread overview]
Message-ID: <1123625568.11092.30.camel@cloud.outersquare.org> (raw)
In-Reply-To: <20050809221935.5601ce98@snowdrop.home>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On Tue, 2005-08-09 at 22:19 +0100, Ciaran McCreesh wrote:
> | but I think having the xml configuration files allows a much more
> | robust configuration.
> 
> How so? Using XML doesn't magically make your data files any different.
> It simply makes them much harder to parse.

That's a matter of opinion.  I see it as a way to abstract away the
configuration and utilize an existing library to handle the parsing.  If
we do want to eliminate outside dependencies (which I think is an
extremely valid point and concern), then we could internally implement a
different configuration format that is easier to parse.  I'd probably go
for something similar to the samba/gdm config files if we were to go
down this road:

selection.conf:
[global]
default_chost = i686-pc-linux-gnu

[i686-pc-linux-gnu]
version=i686-pc-linux-gnu-3.4.4
profile=vanilla

i686-pc-linux-gnu-3.4.4.conf:
[global]
version=i686-pc-linux-gnu-3.4.4
bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.4.4
manpath=blah
infopath=blah

[vanilla]
ldpath=blah
spec=blah

[hardened]
...

So what do people think of these two options?

--Jeremy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-09 22:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 20:53 [gentoo-dev] gcc-config 2.0 development Jeremy Huddleston
2005-08-09 21:19 ` Ciaran McCreesh
2005-08-09 22:12   ` Jeremy Huddleston [this message]
2005-08-09 22:14     ` [gentoo-dev] " Daniel Ostrow
2005-08-09 22:37       ` Paul Varner
2005-08-09 22:43         ` Mike Frysinger
2005-08-09 22:50           ` Ciaran McCreesh
2005-08-09 22:53           ` Diego 'Flameeyes' Pettenò
2005-08-09 22:28     ` Ciaran McCreesh
2005-08-09 22:34     ` Diego 'Flameeyes' Pettenò
2005-08-09 23:48       ` Jeremy Huddleston
2005-08-09 22:47     ` Ferris McCormick
2005-08-10  1:08 ` [gentoo-dev] " Donnie Berkholz

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=1123625568.11092.30.camel@cloud.outersquare.org \
    --to=eradicator@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=toolchain@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