On 21/06/2023 04:17, TOMAS FABRIZIO ORSI wrote:
A warning could be a great way of making the user aware of this situation.
Having said that, if eselect repository is able to check and warn the
user of a not synced overlay(ies) dependency, then the hard bit is done
What I meant is that emerge --sync/eix --sync does this check instead of
eselect repository. To me this makes sense since we can only do this
check *after* syncing. Plus the user can also make changes to repos.conf
without using eselect repository, having the check done post-syncing
covers these cases as well.
You're probably right that once we have some message that says "Warning:
{repo1} is missing, it is required by {repo2}" it should be trivial to
call 'eselect repository enable {repo1}'. This however would require
that profiles/repo_name is always equal to the name entry in
repositories.xml, I'm not sure if this is currently always the case.
Best regards,
Andrew
