For someone behind a restrictive proxy (where git clone git://* fails), access is needed to the http versions of these repos. eg. let's take kde-testing (http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=summary). It can be accessed using: 1./ git://git.overlays.gentoo.org/proj/kde.git 2./ http://git.overlays.gentoo.org/gitroot/proj/kde.git 3./ git+ssh://git@git.overlays.gentoo.org/proj/kde.git Through layman, I only have access to (1), which is blocked by my proxy. Layman, maybe through the use of a special flag (--restrictive-proxy) or maybe on failure of one access method should make these other connection methods available to the user by default. Current workaround: Create my own layman-global.txt file, and point to it in layman.cfg. This isn't a great state of affairs considering that the http server is up and accessible to me. Reproducible: Always
Thanks for the report, sounds like a good suggestion. Assigning to layman maintainer.
Good suggestion indeed but it has been reported already :) I'll try to add a solution to layman-1.2.4. *** This bug has been marked as a duplicate of bug 280472 ***
