-
Notifications
You must be signed in to change notification settings - Fork 700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NimBorg no longer being maintained in original repo #589
Comments
I'm not aware of any that are being maintained. If you can find one then please update the packages.json file. |
should we just delete the entry? |
I'm sure there's a bunch of such unmaintained packages. Unless the repo disappears, we could probably just leave things as is. Eventually when PR #916 gets done and we start testing everything, stuff that doesn't work can get automatically quarantined. Can we close this for now? |
@genotrance - thanks, that PR and listed features look really interesting. I don't see how it will detect abandoned packages (that eg, no longer compile on latest nim Stable/Dev, or, where automated tests fail), but it sounds like you have some kind of plan for that. I'll close this ticket for now |
Hi.
Over in the original repo for NimBorg, the author has mentioned this:
"Sorry chap, I'm not maintaining this repo any more. I'll take it down eventually so that people don't get confused. Note that some core nim devs have forked it, and perhaps other people would keep maintaining it."
micklat/NimBorg#5 (comment)
@dom96 - look into that please?
eg, changing packages json file to point to an actively maintained version.
The text was updated successfully, but these errors were encountered: