From: "Michał Górny" <mgorny@gentoo.org>
To: <gentoo-project@lists.gentoo.org>
Subject: [gentoo-project] RFC: moving API-related DTDs into api.gentoo.org
Date: Tue, 24 Mar 2015 10:37:36 +0100 [thread overview]
Message-ID: <20150324103736.2a43eb85@pomiot.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Hi,
Right now all Gentoo DTS are stored in gentoo CVS repo for
www.gentoo.org. Since we already moved some useful stuff out of there
for api.gentoo.org, I think we should move the relevant DTDs as well.
In particular:
- metadata.dtd -- since it's used by different repositories and not
really www.gentoo.org sites. It would be better if it had permanent
api.gentoo.org URI for apps to fetch.
- mirrors.dtd -- used for mirror XML files stored in api.gentoo.org,
- repositories.dtd -- used for repository XML files stored in a.g.o.
And we should move more DTD as soon as respective XML files are moved
to api.gentoo.org.
Thoughts?
--
Best regards,
Michał Górny
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next reply other threads:[~2015-03-24 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 9:37 Michał Górny [this message]
2015-03-24 11:14 ` [gentoo-project] RFC: moving API-related DTDs into api.gentoo.org Ben de Groot
2015-03-24 12:52 ` Alex Legler
2015-06-02 15:38 ` Mike Frysinger
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=20150324103736.2a43eb85@pomiot.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-project@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