-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[cleanup] remove xmldom
and xmldomparser
#9234
Conversation
Might be nice to create a Nimble packages for the few that use this module :) |
@dom96 But who will take the ownership of those? Shouldn't the original author of those create the nimble packages? |
@dom96 umm. OK. So you are the original author of those. :P |
Speaking from my experience with Emacs project, should Nim create an "obsolete" repo? Packages obsoleted in stdlib can be moved to that repo as nimble packages. That way no one has to take up the ownership responsibility. If someone wants to take up the responsibility, they can claim it, and then only the URL in the nimble packages json needs to change. Ref: Emacs |
So a question .. looks like there's some agreement about obsolete packages. Let's say the repo is named "obsolete-packages", and its URL is https://github.com/nim-lang/obsolete-packages. Then within that repo, we will have:
So, can we have Nimble packages be pointed to different subdirs from the same repo? @dom96? |
@kaushalmodi yeah I know for certain that Nimble supports that. |
Got it: https://github.com/nim-lang/nimble#package-urls |
Btw web/website.ini is dead and should be removed. |
As discussed in #8238: