public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Addition of a new field <remote-id type="debian"> to metadata.xml
Date: Mon, 5 Jun 2017 11:40:15 -0400	[thread overview]
Message-ID: <CAAr7Pr9OrgRaYiQjwkqvD=O2aNEixA5dzXJV-aTGwOJ9yyxjxQ@mail.gmail.com> (raw)
In-Reply-To: <1496476708.10646.1.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]

On Sat, Jun 3, 2017 at 3:58 AM, Michał Górny <mgorny@gentoo.org> wrote:

> On sob, 2017-06-03 at 03:22 +1200, Kent Fredric wrote:
> > On Fri, 02 Jun 2017 16:51:25 +0200
> > Michał Górny <mgorny@gentoo.org> wrote:
> >
> > > ...so if a Gentoo package is split into 40 packages in Debian, are you
> > > going to list all of them?
> >
> > If it would be useful to do so, maybe.
> >
> > But its a text file, people are capable of making judgements about
> > adding 3.2k of text, I hope. ( worst-case, 40 lines of 80 characters
> each )
> >
> > If the text at that size has a use, then, why not?
> >
> > As long as that 40-package example is an exceptional case, where it was
> deemed
> > useful, not the norm.
>
> It's not that exceptional in binary distributions where it's normal to
> split a single source into a few dozen packages (libraries, headers,
> tools, plugins...):
>
> https://packages.debian.org/source/sid/systemd
>
> 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 would argue that specifying source package remotes is what should be done
for every package. UI layers can use the source package remote to look up
metadata for the source package and get a list of the binary packages it
produces when built; maintaining this list inside of Gentoo seems ill
advised. (I could perhaps be swayed by a script where you populate the
source package remote and a tool fills in the binary packages as sourced
from debian sid or whatever.)

Do we really need to store and distribute this data though?

-A


>
> --
> Best regards,
> Michał Górny
>

[-- Attachment #2: Type: text/html, Size: 2517 bytes --]

  parent reply	other threads:[~2017-06-05 15:40 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
2017-06-04 14:54                 ` Kent Fredric
2017-06-05 15:40             ` Alec Warner [this message]
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='CAAr7Pr9OrgRaYiQjwkqvD=O2aNEixA5dzXJV-aTGwOJ9yyxjxQ@mail.gmail.com' \
    --to=antarus@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