From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: Forbid using versions in DESCRIPTION
Date: Tue, 24 Jul 2007 14:30:54 +0100 [thread overview]
Message-ID: <20070724143054.18423d13@snowflake> (raw)
In-Reply-To: <f84u7m$mrc$2@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
On Tue, 24 Jul 2007 15:18:46 +0200
Tiziano Müller <dev-zero@gentoo.org> wrote:
> Ciaran McCreesh schrieb:
> > On Tue, 24 Jul 2007 13:44:52 +0200
> > "Marijn Schouten (hkBst)" <hkBst@gentoo.org> wrote:
> >> Perhaps we should just move DESCRIPTIONs to metadata. That would
> >> make it impossible to use ${PV} and more importantly also remove
> >> some duplication.
> >
> > Got to be careful here. In the past it's been stated that Portage
> > won't use XML for anything that it has to parse.
>
> Well, if/when DESCRIPTION is moved to metadata, this must be changed.
The intention was to stick with things that could be parsed quickly and
easily, without relying upon slow library code. Whether that's still an
issue these days what with the Portage people who were saying that the
loudest not being around any more is up for debate...
Although, at the other end of the scale, Daniel claims that he wanted
to move all ebuild metadata into metadata.xml...
> Unless we change the metadata format as well (to yaml for example :-)
The only specification-compliant yaml parser is written in C, has
only the bottom two layers of the stack and no usable external
bindings... Perhaps you mean "something that's basically yaml except
with reserved string-start characters not handled correctly", in which
case there's Syck...
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-24 13:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 11:11 [gentoo-dev] RFC: Forbid using versions in DESCRIPTION Petteri Räty
2007-07-24 11:36 ` [gentoo-dev] " Christian Faulhammer
2007-07-24 11:44 ` Marijn Schouten (hkBst)
2007-07-24 11:54 ` David Shakaryan
2007-07-24 12:04 ` Petteri Räty
2007-07-24 13:22 ` Tiziano Müller
2007-07-24 12:16 ` Ciaran McCreesh
2007-07-24 12:26 ` Petteri Räty
2007-07-24 13:09 ` Robert Buchholz
2007-07-24 13:18 ` Tiziano Müller
2007-07-24 13:30 ` Ciaran McCreesh [this message]
2007-07-24 13:46 ` Luca Barbato
2007-07-24 13:55 ` Ciaran McCreesh
2007-07-24 14:11 ` Luca Barbato
2007-07-24 14:21 ` Ciaran McCreesh
2007-07-24 14:46 ` Tiziano Müller
2007-07-24 13:36 ` Luca Barbato
2007-07-25 12:17 ` Mike Frysinger
2007-07-24 12:02 ` Tiziano Müller
2007-07-24 12:06 ` Petteri Räty
2007-07-24 12:14 ` Ciaran McCreesh
2007-07-24 12:18 ` Petteri Räty
2007-07-24 13:14 ` Tiziano Müller
2007-07-24 12:53 ` Marijn Schouten (hkBst)
2007-07-25 12:15 ` Mike Frysinger
2007-07-24 12:12 ` David Shakaryan
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=20070724143054.18423d13@snowflake \
--to=ciaranm@ciaranm.org \
--cc=gentoo-dev@lists.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