From: Eric Brown <brown@fastmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Melpa failure :-(
Date: Sat, 18 Apr 2015 12:28:03 -0500 [thread overview]
Message-ID: <m2vbgt2voc.fsf@air.ben-zion.org> (raw)
In-Reply-To: <87twwdl5fm.fsf@mbork.pl> (Marcin Borkowski's message of "Sat, 18 Apr 2015 19:19:57 +0200")
Marcin Borkowski <mbork@mbork.pl> writes:
> Am I the only one to suffer from upgrade failures from time to time?
> Might it be the fault of the pacakge manager, or is using Melpa (not the
> stable version) just asking for trouble? I have to say that I'm on the
> verge of deciding to drop this whole package manager stuff and switching
> to Git or manual install from EW: it will be a bit more work, but at
> least I won't break my Emacs that easily (and I'll be able to easily
> revert to the previous state).
>
No, you are not alone. I recommend using QUELPA, which will allow you to
keep cutting-edge as much as possible, but roll back to a previous
commit if (and when!) you run into trouble.
https://github.com/quelpa/quelpa
You could synthesize a Marmalade/MELPA-stable experience if you dial-in
the commits corresponding to tagged releases.
next prev parent reply other threads:[~2015-04-18 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 17:19 Melpa failure :-( Marcin Borkowski
2015-04-18 17:28 ` Eric Brown [this message]
2015-04-18 17:35 ` Marcin Borkowski
2015-04-18 19:41 ` Memnon Anon
2015-04-18 23:57 ` Drew Adams
2015-04-19 0:09 ` Drew Adams
2015-04-18 23:54 ` Drew Adams
2015-04-18 23:47 ` Drew Adams
2015-04-19 4:10 ` Alexis
[not found] ` <mailman.1078.1429416648.904.help-gnu-emacs@gnu.org>
2015-04-19 23:17 ` gnuist006
2015-04-21 6:13 ` Alexis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vbgt2voc.fsf@air.ben-zion.org \
--to=brown@fastmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.