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
Excise MoinMoin #12713
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
For what it's worth, I removed the moin spkg and modified |
This comment has been minimized.
This comment has been minimized.
Author: John Palmieri |
comment:3
Here's a patch. If we go through with this, should we keep MoinMoin as an optional spkg? Probably we should. |
root repo |
comment:4
Attachment: trac_12713-moin.patch.gz |
Dependencies: #10492 |
comment:5
Replying to @jhpalmieri:
Yes! (Make it an optional spkg.) Incidentally, that's what I was thinking of yesterday as well, and a couple of times before... |
comment:6
I guess this is something which should be discussed properly on sage-devel first... |
This comment has been minimized.
This comment has been minimized.
comment:8
There's slightly more to do: remove the |
This comment has been minimized.
This comment has been minimized.
comment:9
Here are new patches. |
root repo |
Attachment: trac_12713-root.patch.gz scripts repo |
comment:10
Attachment: trac_12713-scripts.patch.gz The Sage library patch conflicts somewhat with #11409. If #11409 is merged first, then the Sage library patch here may be ignored. If this is merged first, then #11409 will need rebasing. |
comment:11
Replying to @jdemeyer:
Should we really remove all traces of MoinMoin (or any kind of wiki) from Sage? If we keep it as an optional (or experimental) spkg, we could treat it as such, just like the others. I.e., just add checks whether it is present / installed, and give messages according to the result. |
comment:12
For an optional spkg, maybe, but do we really maintain (or need to maintain) library/interface support for experimental packages? |
comment:13
Replying to @kini:
Well, I don't have strong feelings about that, but probably there are Sage users out there who really used that stuff... :-) |
comment:14
Since no one on sage-devel objected to the removal of MoinMoin, I think we can do this. If someone wants to restore the functionality, they can just restore the files from |
comment:15
Replying to @jhpalmieri:
It is unlikely that #11409 will get merged any time soon (unfortunately). |
comment:17
The file
should also be removed, and |
comment:18
Okay, here's a new patch which does that. |
Sage library |
comment:19
Attachment: trac_12713-sage.patch.gz Do we also need a patch for sagenb, removing |
This comment has been minimized.
This comment has been minimized.
sagenb |
comment:20
Attachment: trac_12713-sagenb.patch.gz You forgot this (sage library): diff --git a/setup.py b/setup.py
--- a/setup.py
+++ b/setup.py
@@ -1008,7 +1008,6 @@
'sage.server.simple',
'sage.server.notebook',
'sage.server.notebook.compress',
- 'sage.server.wiki',
'sage.server.trac',
'sage.structure', |
Reviewer: Jeroen Demeyer |
comment:21
positive_review if |
This comment has been minimized.
This comment has been minimized.
comment:22
Attachment: 12713-sage-review.patch.gz |
comment:23
Thank you for taking care of that last piece. |
Merged: sage-5.0.beta13 |
We should get rid of MoinMoin as a standard spkg. It is not used by anything in Sage AFAIK. (There has been some discussion about this on sage-devel.) In particular, there was a vote in which (as of March 28) no one objected to removing MoinMoin. There wasn't great consensus about what to do with the package afterwards, but making it "experimental" has support and seems like the right choice: then it is still available but no one has to commit to be the maintainer.
To apply:
spkg/standard/moin-1.9.1.p2.spkg
.Depends on #10492
Depends on #12515
Component: packages: standard
Author: John Palmieri
Reviewer: Jeroen Demeyer
Merged: sage-5.0.beta13
Issue created by migration from https://trac.sagemath.org/ticket/12713
The text was updated successfully, but these errors were encountered: