What's the relationship between this fork and the Iwasawafag/node-potrace repo?
#13
Comments
|
Here. I attempted, in a rather abrupt manner, to "give" this repo to Iwasawafag at an earlier point, but he did even less maintenance work than I have, so I started merging things again. As mentioned elsewhere, I don't have a lot of cycles to carefully evaluate and merge PRs as much as should occur, let alone tackle issues myself, but at least my profile doesn't say "I don't like GitHub". |
jfly
added a commit
to jfly/icons
that referenced
this issue
Sep 18, 2022
WIP: this is super slow? This is nice because it means people don't have to install a native dependency to try things out. Unfortunately, potrace in javascript looks like a bit of a mess: - There's an unmaintained port from 4 years ago: https://github.com/kilobtye/potrace - There's a fork of that which is NodeJS compatible, "with some additions": https://github.com/Iwasawafag/node-potrace - There's this fork of *that* which some additional commits, I can't figure out what it's relationship to the `Iwasawafag` fork is: https://github.com/tooolbox/node-potrace/. (tooolbox/node-potrace#13) - Unfortunately, one or more of the "additions" in the `Iwasawafag` and `toolbox` forks introduce issues with generating fonts, which there's yet another fork designed to fix. See tooolbox/node-potrace#7 and https://github.com/oslllo/potrace/. So, I've introduced a dependency on the `oslllo` fork of a fork of a fork of a fork. 😱
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should I be filing issues here or upstream over at
Iwasawafag?Thanks!
The text was updated successfully, but these errors were encountered: