From: zimoun <zimon.toutoune@gmail.com>
To: Andrew Tropin <andrew@trop.in>
Cc: 44555@debbugs.gnu.org
Subject: [bug#44555] [PATCH] gnu: Add emacs-next-use-package
Date: Tue, 10 Nov 2020 18:16:35 +0100 [thread overview]
Message-ID: <CAJ3okZ1fFBBJdYfqidmMZvZmn_VkgSp9_X4b4wyG=qNKJ0+sLA@mail.gmail.com> (raw)
In-Reply-To: <CABrWRW2F8x4f8WD2d+N8w9i7hNJTRPH_k26ZnELb_W_WRMR_Uw@mail.gmail.com>
Dear,
On Tue, 10 Nov 2020 at 17:13, Andrew Tropin <andrew@trop.in> wrote:
> +(define-public emacs-next-use-package
> + (let ((commit "4fb1f9a68f1e7e7d614652afc017a6652fd029f1")
> + (revision "20200721"))
> + (package/inherit emacs-use-package
> + (name "emacs-next-use-package")
> + (version (git-version "2.4" revision commit))
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/jwiegley/use-package")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> + "073sm0mbxcjysap2bjzf1cl0134jy8a0xig7ywmmd0bm2y8qzfip"))))
> + (propagated-inputs '()))))
> +
Maybe I am missing something, but it is not built using 'emacs-next'.
Why not simply update the package 'emacs-use-package' with a comment
explaining what you already explained?
All the best,
simon
next prev parent reply other threads:[~2020-11-10 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 15:45 [bug#44555] [PATCH] gnu: Add emacs-next-use-package Andrew Tropin
2020-11-10 16:15 ` Andrew Tropin
2020-11-10 17:16 ` zimoun [this message]
2020-11-10 17:56 ` Andrew Tropin
2020-11-10 19:22 ` Michael Rohleder
2020-11-10 19:36 ` Andrew Tropin
2020-11-10 20:32 ` Michael Rohleder
2020-11-11 7:53 ` Andrew Tropin
2020-11-11 9:35 ` Nicolas Goaziou
2020-11-11 10:02 ` bug#44555: " Nicolas Goaziou
2020-11-11 14:33 ` [bug#44555] " Andrew Tropin
2020-11-10 18:00 ` Leo Prikler
2020-11-11 22:42 ` zimoun
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='CAJ3okZ1fFBBJdYfqidmMZvZmn_VkgSp9_X4b4wyG=qNKJ0+sLA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=44555@debbugs.gnu.org \
--cc=andrew@trop.in \
/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).