> On 07 Mar 2015, at 21:10, Thierry Goubier <[email protected]> wrote: > > Le 07/03/2015 20:10, Sven Van Caekenberghe a écrit : >> >>> On 07 Mar 2015, at 19:41, Thierry Goubier <[email protected]> wrote: >>> >>> For example, the following would work : >>> >>> Gofer it >>> url: >>> 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; >>> package: 'HelloWorld'; >>> load >>> >>> Adding that type of Url in both Gofer and Metacello requires overrides in >>> Zn and Metacello: ugly :(:( >> >> I created an issue to study what (if anything) has to change to ZnUrl in >> order to help here: >> >> https://pharo.fogbugz.com/f/cases/15090/ZnUrl-should-be-able-to-better-support-more-yet-unknown-schemes > > Thanks. > >> However, the parsing works fine & correct: >> >> 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git' asZnUrl >> >> which leads me to suspect the problem is in usage. > > Well, I use ZnUrl to decode gitfiletree: urls, so I'm sure I choose a correct > url scheme :) The only extension needed is the dispatch on the scheme of the > url: what ZnUrl can dispatch is hardcoded as a case switch. > > Thierry
Then the problem is in the extension protocol *gofer-core-accessing - for me that is not ZnUrl itself ;-) That being said, I totally agree the code is ugly there, what is the solution ? Doing a subclass based lookup below MCRepository ? Who wants to handle this URL ? Sven
