On Sun, Oct 2, 2016 at 3:48 PM, James Le Cuirot <[email protected]> wrote: > So wouldn't it be great if Portage could handle these gogdownloader:// > URLs?
Yes, it would. But it's just a symptom of the fetching system being inadequate. I gave up on overhauling the git eclasses and a few other things for the same reason, when it became clear the only correct solution is to come up with something better than having portage eval a string, or hack around it by bypassing the fetch phase altogether like the vcs eclasses do. Ideally there would be a mime-mapping configuration in the profile to bind a bash callback with a URI scheme for SRC_URI, so that portage can handle the asynchronous fetching properly and `emerge --fetchonly` isn't broken, while the implementation of the fetcher logic lives either in a repo or a user configuration.
