public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [rfc] layman-global.txt, repositories.xml, layman, overlays.gentoo.org
Date: Thu, 01 Oct 2009 09:35:14 +0200	[thread overview]
Message-ID: <1254382514.29918.71.camel@localhost> (raw)
In-Reply-To: <4AC3847D.9020902@hartwork.org>


[-- Attachment #1.1: Type: text/plain, Size: 1348 bytes --]

Am Mittwoch, den 30.09.2009, 18:17 +0200 schrieb Sebastian Pipping:
> Ciaran McCreesh wrote:
> > Sure. Just periodically fetch the repository centrally. Have a master
> > list of sync URLs with expected repository names, and use that to
> > generate the full master list that includes metadata.
> > 
> > Added bonus: you can quickly remove any repository that no longer
> > exists.
> 
> How long do you want the time frame for add-meta-data-or-get-kicked
> to be?  If half the repos don't not make it will kicking them help
> anybody?
Yes, then they're not maintained. And unmaintained overlays tend to
contain even more broken ebuilds than others.

>   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 the
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 to
convert it to a new format on the fly. As long as you keep using xml you
can then change the complete format in a new schema version.


-- 
Tiziano Müller
Gentoo Linux Developer
Areas of responsibility:
  Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor
E-Mail   : dev-zero@gentoo.org
GnuPG FP : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30

[-- Attachment #1.2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3551 bytes --]

  reply	other threads:[~2009-10-01  7:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 18:23 [gentoo-dev] [rfc] layman-global.txt, repositories.xml, layman, overlays.gentoo.org Sebastian Pipping
2009-09-29 20:36 ` volkmar
2009-09-30  1:36   ` Sebastian Pipping
2009-09-30 14:26 ` Tiziano Müller
2009-09-30 15:36   ` Sebastian Pipping
2009-09-30 15:48     ` Fabian Groffen
2009-09-30 15:57       ` Sebastian Pipping
2009-10-01  7:27         ` Tiziano Müller
2009-10-01 14:17           ` Sebastian Pipping
2009-09-30 14:39 ` Ciaran McCreesh
2009-09-30 15:51   ` Sebastian Pipping
2009-09-30 15:53     ` Ciaran McCreesh
2009-09-30 16:00       ` Sebastian Pipping
2009-09-30 16:04         ` Ciaran McCreesh
2009-09-30 16:17           ` Sebastian Pipping
2009-10-01  7:35             ` Tiziano Müller [this message]
2009-10-01  8:48               ` Robert Buchholz
2009-10-01 13:35               ` Sebastian Pipping
2009-10-03  0:30     ` Sebastian Pipping

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=1254382514.29918.71.camel@localhost \
    --to=dev-zero@gentoo.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