public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Schmaus <flow@gentoo.org>
To: TOMAS FABRIZIO ORSI <torsi@fi.uba.ar>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Eselect repository feature request
Date: Tue, 20 Jun 2023 15:44:03 +0200	[thread overview]
Message-ID: <30d4b57b-734f-bd42-4427-15389256e80f@gentoo.org> (raw)
In-Reply-To: <CAHTSwYiGLSRByoZp63-Gda7sXA5SBY649-BD8_TYvyapY2NsWQ@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2441 bytes --]

On 18.06.23 22:39, TOMAS FABRIZIO ORSI wrote:
> Hello gentoo devs. The other day I made a feature suggestion to the 
> eselect repository github page. (Here's the link: 
> https://github.com/projg2/eselect-repository/issues/20 
> <https://github.com/projg2/eselect-repository/issues/20>).
> Michał Górny suggested that I should contact the gentoo-dev mailing list 
> with my suggestion, so here it is: My suggestion is to make it possible 
> for eselect repository to manage overlay dependencies.
> 
> As it stands, and as far as I'm concerned, there is no "proper" way of 
> having an ebuild dependency from another overlay. So overlay writers 
> have to copy ebuilds from other overlays or rewrite them. This implies 
> synchronization issues (where the "copied" ebuilds get out of sync from 
> the original ebuild) and time loss (people writing the same ebuild more 
> than once).
> 
> Michał Górny suggested that I should make an edit to the 
> repositories.xml file in order to tackle the issue.
> 
> This is my general idea:
> (I am using the github template as an example, but the idea should apply 
> to all other templates. I got this file from 
> https://github.com/gentoo/api-gentoo-org/blob/master/files/overlays/repositories.xml <https://github.com/gentoo/api-gentoo-org/blob/master/files/overlays/repositories.xml>).
> 
>    * GITHUB TEMPLATE
>      <repo quality="experimental" status="unofficial">
>        <name>XXXXX</name>
>        <description lang="en">XXXXXX</description>
>        <homepage>https://github.com/XXXX/xxxx 
> <https://github.com/XXXX/xxxx></homepage>
>        <owner type="person">
>          <email>XXXXX</email>
>          <name>XXXXX</name>
>        </owner>
>        <source type="git">https://github.com/XXXX/xxxx.git 
> <https://github.com/XXXX/xxxx.git></source>
>        <source type="git">git+ssh://git@github.com/XXXX/xxxx.git 
> <http://git@github.com/XXXX/xxxx.git></source>
>        <feed>https://github.com/XXXX/xxxx/commits/master.atom 
> <https://github.com/XXXX/xxxx/commits/master.atom></feed>
>        <dependencies>
>            <name>overlayName</name>
>        </dependencies>
>      </repo>

Isn't that duplicating the information of metadata/layout.conf's 
'master' key-value pair [1]?

- Flow

1: 
https://wiki.gentoo.org/wiki/Repository_format/metadata/layout.conf#masters

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17843 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2023-06-20 13:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18 20:39 [gentoo-dev] Eselect repository feature request TOMAS FABRIZIO ORSI
2023-06-20 13:44 ` Florian Schmaus [this message]
2023-06-20 14:41   ` TOMAS FABRIZIO ORSI
2023-06-20 17:08     ` Florian Schmaus
2023-06-20 17:26       ` Mike Gilbert
2023-06-20 18:07         ` Andrew Ammerlaan
2023-06-21  2:17           ` TOMAS FABRIZIO ORSI
2023-06-21  7:15             ` Andrew Ammerlaan
2023-06-21 13:40               ` TOMAS FABRIZIO ORSI
2023-06-21 13:58                 ` Andrew Ammerlaan
2023-06-21 14:12                   ` TOMAS FABRIZIO ORSI
2023-06-21 14:30                     ` Andrew Ammerlaan
2023-06-21 14:43                       ` TOMAS FABRIZIO ORSI
2023-06-21 15:07                         ` Mike Gilbert
2023-06-21 15:34                           ` TOMAS FABRIZIO ORSI
2023-06-21 15:41         ` Florian Schmaus
2023-06-21 15:56           ` Mike Gilbert
2023-06-21 16:47             ` TOMAS FABRIZIO ORSI
2023-06-21 17:45               ` Mike Gilbert
2023-06-21 17:59                 ` TOMAS FABRIZIO ORSI
2023-06-24 17:02                   ` Florian Schmaus
     [not found]                   ` <8ef315e8-a9fe-c33a-7ab4-ef7653c10cb9@gentoo.org>
     [not found]                     ` <CAHTSwYiXiO2OMU4A5TiunrEy+Zs+UMFwoV3wmSdEW5RNrS5xJA@mail.gmail.com>
     [not found]                       ` <CAHTSwYgO7F2gOOSWHDOBFry4YBb1a1KSy9g8h4iUh+rK0GFRuQ@mail.gmail.com>
     [not found]                         ` <2d264617-f48e-d129-adc2-10aac6cef2a2@gentoo.org>
2023-07-12 18:03                           ` TOMAS FABRIZIO ORSI
2023-06-21 17:59                 ` Anna
2023-06-21 16:49             ` Florian Schmaus
2023-06-21 17:28               ` Mike Gilbert
2023-06-21 18:42               ` Sam James
2023-06-21 19:03                 ` TOMAS FABRIZIO ORSI
2023-06-21 19:16                   ` Sam James

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=30d4b57b-734f-bd42-4427-15389256e80f@gentoo.org \
    --to=flow@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=torsi@fi.uba.ar \
    /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