Hi Phil, On Fri, Dec 13, 2013 at 4:57 AM, Phillip Lord <phillip.l...@newcastle.ac.uk> wrote: > Bozhidar Batsov <bozhidar.bat...@gmail.com> writes: >> On Tuesday, November 19, 2013 4:56:05 PM UTC+2, Phillip Lord wrote: >>> I discovered one of the reasons for my issues with stability yesterday. >>> The version of clojure-test-mode on marmalade still depends on nrepl >>> (rather than cider), so, despite my best efforts to remove nrepl.el it >>> was still getting pulled back in. >> >> Marmalade is a huge problem these days - frequent outages, not to mention >> many package uploads (including cider 0.4) got corrupted and Nic hasn't >> been able to figure out what's going on there. >> I'd suggest to everyone to use MELPA for the time being. > > So, I have used MELPA before, but I found living on the bleeding edge > for all of my packages is bit painful; the overall stability of my Emacs > setup dropped considerably. I fear this will remain while many package > developers use a "dirty head" versioning system (myself included).
That has completely been my experience. Continuous Deployment _requires_ Continuous Integration and pretty much all of the emacs package developers out there don't have the time to do CI correctly so Continuous Deployment simply equals lots of pain on the users end as things get broken accidentally. > I don't mind doing this for one or two packages where I want bleeding > edge, but I haven't worked out how to get package.el to pick packages > from different repos. You might consider playing with something that I've had in my incubator file for awhile: https://github.com/timvisher/.emacs.d/blob/c8fa14315825f722f9995e8dd1e888c6b81321e9/timvisher/timvisher_incubator.el#L16-L28 > I agree with you about problems with marmalade. What we need is a way > for devs to specify the latest stable version (by commit, branch or tag) > in their Emacs packages. That would mean that, like marmalade, the > developer would control which version is considered stable, but could do > so purely with their VC. Wordpress plugins use something similar. I assume you mean something over and above the `Version` ELPA header? Obviously, that depends on package maintainers following things like SNAPSHOT versioning (which ELPA doesn't accept) or Semantic Versioning to tip people off as to what is considered stable. I think the general attitude I'm seeing amongst some of the package maintainers out there is that the idea of versioning is a farse because they always intend to maintain stable HEADs so HEAD is as stable as your ever going to get. That's a shame, but I get the sentiment. So the responsibility for deciding what is stable or not falls to us, the package users. That's, unfortunately, an area where ELPA is woefully inadequate at this time. We have no way of specifying that we want a particular version of a package. That's a basic requirement of any true dependency management system and for whatever reason the Emacs devs did not deign to include it yet. I, at this point, would be fine with specifying a version _or_ commit depending on what package repo I'm pointing at. Didn't realize I'd rant this morning. :( -- In Christ, Timmy V. http://blog.twonegatives.com/ http://five.sentenc.es/ -- Spend less time on mail -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
