Closed DarwinAwardWinner closed 12 years ago
Assuming that all the packages are equivalent and mirrored I don't see any reason not to.
+1 from me.
Yeah, how much trust do we have in that mirrors (update schedule, etc)? I'm not sure about using that as a way to avoid the flooding problem, I think we should really be addressing it.
According to this accouncement, the Github mirror is pushed hourly. I'd say that's pretty good.
As for rate-limiting HTTP requests to emacswiki, I think I have an idea on how to do that. I'll post about that in the appropriate issue.
Oh so that's pushed by the EmacsWiki maintainer himself, that's all different then. I would be ok to reconsider and just use the mirror then.
I think for the 4.1 release we can take the easy way out and use the Github mirror as the download source for EmacsWiki packages, thus sidestepping the rate-limiting issue entirely for now. Then we can add the rate-limiting code later when it is ready. What do you think?
Knowing that the mirror is maintained by the same Emacs Fame who already maintains EmacsWiki itself, I agree.
Apparently there is a mirror of Emacswiki on Github: https://github.com/emacsmirror/emacswiki.org/tree/master
You can use it by doing
(setq el-get-emacswiki-base-url "https://raw.github.com/emacsmirror/emacswiki.org/master/")
, as reported here: https://github.com/DarwinAwardWinner/dotemacs/issues/2I think we should consider making this the default base URL for Emacswiki. People won't notice the difference, except that we no longer need to worry about flooding emacswiki.org's bandwidth when installing lots of stuff from Emacswiki.
I can easily add an automated test to ensure that it functions correctly as a mirror for Emacswiki.