From: Andrey Utkin <andrey_utkin@fastmail.com>
To: Kent Fredric <kentnl@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Addition of a new field <remote-id type="debian"> to metadata.xml
Date: Sun, 4 Jun 2017 13:56:52 +0100 [thread overview]
Message-ID: <20170604125652.GA27391@dell-m4800> (raw)
In-Reply-To: <20170603201932.6381c8ba@katipo2.lan>
On Sat, Jun 03, 2017 at 08:19:32PM +1200, Kent Fredric wrote:
> 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"
It is common for debian package names contain version numbers, besides
other ugliness:
https://packages.debian.org/search?keywords=libavcodec&searchon=names&suite=stable§ion=all
You have searched for packages that names contain libavcodec in suite(s)
stable, all sections, and all architectures. Found 4 matching packages.
Package libavcodec-dev
Package libavcodec-extra
Package libavcodec-extra-56
Package libavcodec56
Obviously numbered package name libavcodec56 can be an attribute of
exact ebuild, but not of a Gentoo package.
With this ugliness of Debian packages naming, I'm afraid the proposed
change won't take off.
next prev parent reply other threads:[~2017-06-04 12:56 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
2017-06-04 12:56 ` Andrey Utkin [this message]
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=20170604125652.GA27391@dell-m4800 \
--to=andrey_utkin@fastmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kentnl@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