From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Addition of a new field <remote-id type="debian"> to metadata.xml
Date: Sat, 3 Jun 2017 20:19:32 +1200 [thread overview]
Message-ID: <20170603201932.6381c8ba@katipo2.lan> (raw)
In-Reply-To: <1496476708.10646.1.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Sat, 03 Jun 2017 09:58:28 +0200
Michał Górny <mgorny@gentoo.org> wrote:
> and that's a small one. I guess we could avoid this if you restricted
> those remotes to the source package used to build them all.
I think in the event they're a form of conventional
foo
foo-dev
foo-dbg
etc, under the knowledge that those things can't possibly map to other
gentoo packages, we should codify only the first of those, and then have
it placed on the iteroperating code to make logical inferences from
that.
"foo-dev" in a search query would map to "foo" if no "foo-dev" existed.
But yeah, lots of complexity there.
That's why I'd just say those facets shouldn't really be mapped
explicitly.
The general pattern being:
"If a debian id can be conjugated from another debian id by guessing
with a generic algorithm, only index the former"
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-03 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 21:18 [gentoo-dev] [RFC] Addition of a new field <remote-id type="debian"> to metadata.xml Jonas Stein
2017-06-02 1:09 ` Kent Fredric
2017-06-02 1:36 ` Daniel Campbell
2017-06-02 6:59 ` Kent Fredric
2017-06-03 7:41 ` Daniel Campbell
2017-06-02 6:16 ` Jonas Stein
2017-06-02 7:07 ` Vadim A. Misbakh-Soloviov
2017-06-02 14:38 ` Kent Fredric
2017-06-02 14:51 ` Michał Górny
2017-06-02 15:22 ` Kent Fredric
2017-06-03 7:58 ` Michał Górny
2017-06-03 8:19 ` Kent Fredric [this message]
2017-06-04 12:56 ` Andrey Utkin
2017-06-04 14:54 ` Kent Fredric
2017-06-05 15:40 ` Alec Warner
2017-06-05 15:51 ` Kent Fredric
2017-08-30 20:00 ` 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=20170603201932.6381c8ba@katipo2.lan \
--to=kentnl@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