public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [RFC] Addition of a new field <remote-id type="debian"> to metadata.xml
Date: Thu, 1 Jun 2017 23:18:22 +0200	[thread overview]
Message-ID: <d10a81a9-5c7f-743b-7eea-925de2097ab7@gentoo.org> (raw)

Hello,

this RFC is about the addition of a new field
<remote-id type="debian">
to metadata.xml

The field should contain a list of the equivalent debian package names,
or a defined string for NONE or UNSET.
A feature request ticket was prepared here:
https://bugs.gentoo.org/show_bug.cgi?id=619132


1. Motivation
=============
Gentoo users and users of debian based distributions profit from linked
packages:

* can be used to embed screenshots from https://screenshots.debian.net
in https://packages.gentoo.org/

* when writing/reading documentation which is written for debian like
Linux distributions

* scripts can automatically compare latest versions, critical bugs, from
debian-like distributions and alert the interested maintainer or prepare
statistics. A greasemonkey script can show a link in bugzilla and the
maintainer can see open/solved bugs and the solutions on other
distributions.

* package names hardly differ between *buntu, mint, and debian so we
cover a broad spectrum

* Users who switch from debian like systems to gentoo, or administrate
gentoo and debian like systems at the same time can find the
corresponding packages quickly


2. Specification
================
A space separated list of the corresponding debian packages should be
written in the field
<remote-id type="debian"> </remote-id>

It should be NONE, if debian has no corresponding package.
UNSET or no field, if the creator of the ebuild did not set the field (yet).

example:
app-arch/tar/metadata.xml
<remote-id type="debian">tar</remote-id>

app-office/libreoffice-bin/metadata.xml
<remote-id type="debian">libreoffice libreoffice-base libreoffice-base
libreoffice-dev libreoffice-dmaths libreoffice-draw
libreoffice-evolution libreoffice-impress</remote-id>


3. Backwards compatibility
==========================
Fully compatible, no negative side effects to expect.


4. Comments
===========

What do you think?
Should we exclude translation packages, or just add them all?

-- 
Best regards,
Jonas Stein


             reply	other threads:[~2017-06-01 21:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 21:18 Jonas Stein [this message]
2017-06-02  1:09 ` [gentoo-dev] [RFC] Addition of a new field <remote-id type="debian"> to metadata.xml 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
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=d10a81a9-5c7f-743b-7eea-925de2097ab7@gentoo.org \
    --to=jstein@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