From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-37893-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1MtLoS-0001OI-By
	for garchives@archives.gentoo.org; Thu, 01 Oct 2009 13:35:16 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 4F017E08EC;
	Thu,  1 Oct 2009 13:35:15 +0000 (UTC)
Received: from smtprelay08.ispgateway.de (smtprelay08.ispgateway.de [80.67.31.31])
	by pigeon.gentoo.org (Postfix) with ESMTP id 27EA6E08EC
	for <gentoo-dev@lists.gentoo.org>; Thu,  1 Oct 2009 13:35:15 +0000 (UTC)
Received: from [85.177.89.76] (helo=[192.168.0.3])
	by smtprelay08.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.68)
	(envelope-from <webmaster@hartwork.org>)
	id 1MtLnH-0004mv-77
	for gentoo-dev@lists.gentoo.org; Thu, 01 Oct 2009 15:34:03 +0200
Message-ID: <4AC4B011.1070704@hartwork.org>
Date: Thu, 01 Oct 2009 15:35:13 +0200
From: Sebastian Pipping <webmaster@hartwork.org>
User-Agent: Thunderbird 2.0.0.22 (X11/20090820)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [rfc] layman-global.txt, repositories.xml, layman,
 overlays.gentoo.org
References: <4AC0FF26.4030608@hartwork.org>	 <20090930153906.070cf662@snowcone>	<4AC37E66.5030708@hartwork.org>	 <20090930165340.79a93e46@snowcone>	<4AC3808D.7010205@hartwork.org>	 <20090930170457.7b8d2d14@snowcone>  <4AC3847D.9020902@hartwork.org> <1254382514.29918.71.camel@localhost>
In-Reply-To: <1254382514.29918.71.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-1
X-Df-Sender: 874396
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 10e1790b-e22b-442f-823a-d21f8292448e
X-Archives-Hash: c724f177293c1bfe5ebae9f0e7bda6fb

Tiziano M=FCller wrote:
>>   What if that metadata format changes later or is extended by
>> additional required entries?
> How about using the power of xml and version the schemas? As long as th=
e
> metadata-file specifies the respective dtd/xsd/relaxng you know exactly
> how to validate (and parse) it and may apply a xsl-trafo if necessary t=
o
> convert it to a new format on the fly. As long as you keep using xml yo=
u
> can then change the complete format in a new schema version.

We are version the schemas already.  My point is that we would need to
wait for the overlay maintainers once again to update their metadata.
Transforming does not save us as we are missing new data.


Sebastian