From: Alex Kost <alezost@gmail.com>
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add emacs-better-defaults.
Date: Sat, 28 May 2016 17:05:46 +0300 [thread overview]
Message-ID: <87h9di1dmt.fsf@gmail.com> (raw)
In-Reply-To: <1464358215-4416-2-git-send-email-dthompson2@worcester.edu> (David Thompson's message of "Fri, 27 May 2016 10:10:15 -0400")
David Thompson (2016-05-27 17:10 +0300) wrote:
> * gnu/packages/emacs.scm (emacs-better-defaults): New variable.
> ---
> gnu/packages/emacs.scm | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
>
> diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
> index 5d6db5a..105c25d 100644
> --- a/gnu/packages/emacs.scm
> +++ b/gnu/packages/emacs.scm
> @@ -1706,3 +1706,24 @@ It is recommended to use @code{clojure-mode} with paredit or smartparens.")
> The purpose of this library is to wrap all the quirks and hassle of
> @code{package.el} into a sane API.")
> (license license:gpl3+)))
> +
> +(define-public emacs-better-defaults
> + (package
> + (name "emacs-better-defaults")
> + (version "0.1.3")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (string-append "http://stable.melpa.org/packages/better-defaults-"
> + version ".el"))
My understanding is that we prefer to retrieve a source directly from
the upstream, so it is better to use:
https://github.com/technomancy/better-defaults/archive/0.1.3.tar.gz
Otherwise, LGTM.
> + (sha256
> + (base32
> + "0lvpmja8i8v10lbcvzj6pd7vn9c7gnlbcddd416g2pjq0yydydgf"))))
> + (build-system emacs-build-system)
> + (home-page "https://github.com/technomancy/better-defaults")
> + (synopsis "Better defaults for Emacs")
> + (description
> + "Better defaults attempts to address the most obvious deficiencies of the
> +Emacs default configuration in uncontroversial ways that nearly everyone can
> +agree upon.")
> + (license license:gpl3+)))
--
Alex
next prev parent reply other threads:[~2016-05-28 14:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:10 [PATCH 1/2] build: emacs: Handle sources that are a single elisp file David Thompson
2016-05-27 14:10 ` [PATCH 2/2] gnu: Add emacs-better-defaults David Thompson
2016-05-28 14:05 ` Alex Kost [this message]
2016-05-28 15:37 ` Ludovic Courtès
2016-05-30 15:11 ` Thompson, David
2016-05-31 16:59 ` Mark H Weaver
2016-05-31 17:16 ` Thompson, David
2016-06-01 2:07 ` Mark H Weaver
2016-05-31 20:53 ` Alex Kost
2016-05-31 20:55 ` Thompson, David
2016-05-28 13:59 ` [PATCH 1/2] build: emacs: Handle sources that are a single elisp file Alex Kost
2016-05-28 15:36 ` Ludovic Courtès
2016-05-28 19:05 ` Alex Kost
2016-05-29 21:50 ` Ludovic Courtès
2016-05-30 10:14 ` Alex Kost
2016-05-30 11:55 ` Catonano
2016-05-30 12:42 ` Catonano
2016-05-30 15:12 ` Thompson, David
2016-05-30 16:27 ` Solving the ‘package-name->name+version’ name conflict. (was: [PATCH 1/2] build: emacs: Handle sources that are a single elisp file.) Mathieu Lirzin
2016-06-08 12:44 ` Solving the ‘package-name->name+version’ name conflict Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9di1dmt.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).