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