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 > ). > 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 ). > >   * GITHUB TEMPLATE >     >       XXXXX >       XXXXXX >       https://github.com/XXXX/xxxx > >       >         XXXXX >         XXXXX >       >       https://github.com/XXXX/xxxx.git > >       git+ssh://git@github.com/XXXX/xxxx.git > >       https://github.com/XXXX/xxxx/commits/master.atom > >       >           overlayName >       >     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