Layman helps the user manage different overlays. A quick overview of those available (layman -L) shows that three (possibly four) different content tracking packages are used, rsync, subversion, Git (and possibly Tar?).
I tried adding an overlay that uses Git, but was told that I didn't have Git installed.
I think it would be useful to have appropriate USE flags for layman to pull in Git/rsync/subversion as required by the user.
Steps to Reproduce:
1. emerge layman
2. layman -L
3. layman -a mpd
If dev-util/git isn't already installed....
* Failed to add overlay "mpd".
* Error was: Binary /usr/bin/git seems to be missing! Overlay type "git" not supported. Did you emerge dev-util/git?
Nice if you could...
echo 'app-portage/layman [git | subversion | rsync]' >> /etc/portage/package.use
layman -a mpd
...and the overlay would be installed because the relevant tracking package was pulled in when layman was installed.
That's what the message is for there; we are not adding dependencies to the ebuild.
*** This bug has been marked as a duplicate of bug 168203 ***
(In reply to comment #1)
> That's what the message is for there; we are not adding dependencies to the
> *** This bug has been marked as a duplicate of bug 168203 ***
I did read the message and am aware I could install Git by hand, just thought that was the point of having USE flags.
Well, I see you point, but we've been getting bugs to the opposite effect when the dependencies were there, so... can't satisfy everyone I guess - so instead the messages have been improved to provide the info in a friendly way when you don't have the needed VCS app installed.
Also, looking at the ebuild there is a test for subversion in there, so why not the others?
Well since "most available overlays are offered via dev-util/subversion", that's it.