Origianl post: https://github.com/projg2/eselect-repository/issues/20 It has happened to me a couple of times that my personal overlay makes use of packages that are present in other overlays (that are not in the main gentoo or even guru tree) As far as I am concerned, the best way to handle this situation is to copy the necessary ebuild. However this approach has a couple of problems: Having to sync the copied ebuild There are 2 ebuilds that do the same thing, which can get out of sync fairly easily My humble suggestion: Having an optional parameter on the profiles directory called dependecies. Said file could be a list of names / links to the overlays that the selected overlay depends on. This does imply an update to the overlay standard; however it should be backwards compatible (if the file is not present, then it is assumed that it is self contained) Michał Górny pointed out that the masters key in metadata/layout.conf can already be used for this purpose. Michał also pointed out that, in order to be able to manage the dependencies with eselect-repository, the repositories.xml file has to include said dependencies. (https://github.com/projg2/eselect-repository/issues/20#issuecomment-1579098528)
I'm not sure who would "own" this type of request, so I'm assigning it to mgorny since you have already discussed this with him.
