Dependency to me.raynes/hickory prevents a project from using the original hickory as a dependency

[luxbock]

I have a project that has a dependency to hickory 0.5.3. Trying to:

(require '[me.raynes.laser :as l])

Results in:

CompilerException java.lang.RuntimeException: Unable to resolve var: hickory/unescaped in this context, compiling:(me/raynes/laser.clj:14:1) 

Yet I can't use me.raynes/hickory for my project as it depends on features of hickory not present in your fork. So far I haven't been able to figure out how to get around this issue. What was the reason for your fork and would it be possible to perhaps merge those into the hickory main to get around this sort of issue?

[Raynes]

There were some changes I needed to make to hickory, particularly involving that unescaped function, that David wasn't interested in having in hickory. I don't really have much choice but to have a fork of the project, unfortunately.

I'm not opposed to merging upstream into my fork if possible, however.

[luxbock]

Would it be possible to rename your fork of hickory to me.raynes/hickory? I think that should solve it. At the moment a project that uses Laser can't have any dependencies that depend on the main line of hickory.