From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for a Universal Remote-ID File
Date: Sat, 23 Sep 2023 10:47:17 -0400 [thread overview]
Message-ID: <283422772ae25e326b757d57e84f8b2acd6b3628.camel@gentoo.org> (raw)
In-Reply-To: <87o7ht0x86.fsf@gentoo.org>
On Sat, 2023-09-23 at 15:39 +0100, Sam James wrote:
>
> At the moment, we bundle the DTD in pkgcore. If we just shoved it in
> metadata/ instead in the main repo, we don't have that kind of problem.
>
I might be missing something obvious, but what I mean is, suppose we
have this plain-text mapping of remote-id names to URLs. How do we get
the list of keys (valid remote-id names) into the DTD? Even if both
files are inside metadata/, there's another step that needs to happen.
next prev parent reply other threads:[~2023-09-23 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 18:40 [gentoo-dev] Proposal for a Universal Remote-ID File Siddhanth Rathod
2023-09-23 7:17 ` Ulrich Mueller
2023-09-23 14:16 ` Sam James
2023-09-23 14:35 ` Michael Orlitzky
2023-09-23 14:39 ` Sam James
2023-09-23 14:47 ` Michael Orlitzky [this message]
2023-09-24 17:44 ` Siddhanth Rathod
2023-09-24 20:15 ` Michael Orlitzky
2023-09-23 15:15 ` Ionen Wolkens
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=283422772ae25e326b757d57e84f8b2acd6b3628.camel@gentoo.org \
--to=mjo@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