| 1 |
Am Mittwoch, den 30.09.2009, 18:17 +0200 schrieb Sebastian Pipping: |
| 2 |
> Ciaran McCreesh wrote: |
| 3 |
> > Sure. Just periodically fetch the repository centrally. Have a master |
| 4 |
> > list of sync URLs with expected repository names, and use that to |
| 5 |
> > generate the full master list that includes metadata. |
| 6 |
> > |
| 7 |
> > Added bonus: you can quickly remove any repository that no longer |
| 8 |
> > exists. |
| 9 |
> |
| 10 |
> How long do you want the time frame for add-meta-data-or-get-kicked |
| 11 |
> to be? If half the repos don't not make it will kicking them help |
| 12 |
> anybody? |
| 13 |
Yes, then they're not maintained. And unmaintained overlays tend to |
| 14 |
contain even more broken ebuilds than others. |
| 15 |
|
| 16 |
> What if that metadata format changes later or is extended by |
| 17 |
> additional required entries? |
| 18 |
How about using the power of xml and version the schemas? As long as the |
| 19 |
metadata-file specifies the respective dtd/xsd/relaxng you know exactly |
| 20 |
how to validate (and parse) it and may apply a xsl-trafo if necessary to |
| 21 |
convert it to a new format on the fly. As long as you keep using xml you |
| 22 |
can then change the complete format in a new schema version. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Tiziano Müller |
| 27 |
Gentoo Linux Developer |
| 28 |
Areas of responsibility: |
| 29 |
Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor |
| 30 |
E-Mail : dev-zero@g.o |
| 31 |
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30 |
Archives