From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emacs/bind-key/files/, app-emacs/bind-key/
Date: Thu, 21 Apr 2022 01:54:12 +0000 (UTC) [thread overview]
Message-ID: <1650505489.2dd3b162344dc151518f776d91e80a84c09051c4.xgqt@gentoo> (raw)
commit: 2dd3b162344dc151518f776d91e80a84c09051c4
Author: Maciej Barć <xgqt <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 21 00:47:00 2022 +0000
Commit: Maciej Barć <xgqt <AT> gentoo <DOT> org>
CommitDate: Thu Apr 21 01:44:49 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2dd3b162
app-emacs/bind-key: new package; add version 2.4.1
Signed-off-by: Maciej Barć <xgqt <AT> gentoo.org>
app-emacs/bind-key/Manifest | 1 +
app-emacs/bind-key/bind-key-2.4.1.ebuild | 27 +++++++++++++++++++++++++++
app-emacs/bind-key/files/50bind-key-gentoo.el | 1 +
app-emacs/bind-key/metadata.xml | 13 +++++++++++++
4 files changed, 42 insertions(+)
diff --git a/app-emacs/bind-key/Manifest b/app-emacs/bind-key/Manifest
new file mode 100644
index 000000000000..9aad8f0492a8
--- /dev/null
+++ b/app-emacs/bind-key/Manifest
@@ -0,0 +1 @@
+DIST use-package-2.4.1.tar.gz 124368 BLAKE2B 5eaa6f500234d86651e155fa5360362c5e2696a8b258d5785a02b94f4ccacc6a9815e0b53f663684cef1cc9aa6c6812a5f59e04de3a3d7c5ac36e9dfb6ea09ea SHA512 7248243dbddd939eb1ef9e76f9410265ed1cc48398745f593b57122261a6bb3bf4ab40392b6f29476ca33922f7087a52596a87968cf4914e5ed82db6c513bbbf
diff --git a/app-emacs/bind-key/bind-key-2.4.1.ebuild b/app-emacs/bind-key/bind-key-2.4.1.ebuild
new file mode 100644
index 000000000000..eca71e9ca659
--- /dev/null
+++ b/app-emacs/bind-key/bind-key-2.4.1.ebuild
@@ -0,0 +1,27 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit elisp
+
+DESCRIPTION="Simple way to manage personal keybindings"
+HOMEPAGE="https://github.com/jwiegley/use-package/"
+SRC_URI="https://github.com/jwiegley/use-package/archive/${PV}.tar.gz
+ -> use-package-${PV}.tar.gz"
+S="${WORKDIR}"/use-package-${PV}
+
+LICENSE="GPL-3+"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+SITEFILE="50${PN}-gentoo.el"
+
+src_compile() {
+ elisp-compile ${PN}.el
+}
+
+src_install() {
+ elisp-site-file-install "${FILESDIR}/${SITEFILE}"
+ elisp-install ${PN}.el{,c}
+}
diff --git a/app-emacs/bind-key/files/50bind-key-gentoo.el b/app-emacs/bind-key/files/50bind-key-gentoo.el
new file mode 100644
index 000000000000..431f7e90ae73
--- /dev/null
+++ b/app-emacs/bind-key/files/50bind-key-gentoo.el
@@ -0,0 +1 @@
+(add-to-list 'load-path "@SITELISP@")
diff --git a/app-emacs/bind-key/metadata.xml b/app-emacs/bind-key/metadata.xml
new file mode 100644
index 000000000000..3f12e84d7508
--- /dev/null
+++ b/app-emacs/bind-key/metadata.xml
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+
+<pkgmetadata>
+ <maintainer type="project">
+ <email>gnu-emacs@gentoo.org</email>
+ <name>Gentoo GNU Emacs project</name>
+ </maintainer>
+ <upstream>
+ <bugs-to>https://github.com/jwiegley/use-package/issues/</bugs-to>
+ <remote-id type="github">jwiegley/use-package</remote-id>
+ </upstream>
+</pkgmetadata>
reply other threads:[~2022-04-21 1:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1650505489.2dd3b162344dc151518f776d91e80a84c09051c4.xgqt@gentoo \
--to=xgqt@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox