Re: [gentoo-dev] Eselect repository feature request

[TOMAS FABRIZIO ORSI <torsi@fi.uba.ar>]

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

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

Yes, I agree that it would be duplicating that information. As a matter of
fact, Michał Górny pointed the same thing out.
However, Michał also added, quote: "What's really lacking here is support
for specifying dependencies via repositories.xml. Once such a thing is
implemented, We can look into having eselect-repository handle that once
it's specified." (Here's the link to the conversation:
https://github.com/projg2/eselect-repository/issues/20#issuecomment-1579098528
)
That's why I added the <dependencies> line in the repositories.xml template.

Having said that, maybe the information present in the masters key could be
used to add the overlay dependencies in the repositories present in the xml
file as of today.

Thank you for your reply,

--
Best regards,
- Tomas Fabrizio Orsi


El mar, 20 jun 2023 a las 10:44, Florian Schmaus (<flow@gentoo.org>)
escribió:

> 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 #2: Type: text/html, Size: 6262 bytes --]