From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-vim/splice/
Date: Sat, 4 Apr 2020 12:15:58 +0000 (UTC) [thread overview]
Message-ID: <1586002542.7c84463c18f4118b175584c993a59e1e9a372ae9.zlogene@gentoo> (raw)
commit: 7c84463c18f4118b175584c993a59e1e9a372ae9
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 4 12:15:42 2020 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sat Apr 4 12:15:42 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7c84463c
app-vim/splice: mark stable
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
app-vim/splice/splice-1.1.0-r2.ebuild | 35 -----------------------------------
app-vim/splice/splice-1.1.0-r3.ebuild | 2 +-
2 files changed, 1 insertion(+), 36 deletions(-)
diff --git a/app-vim/splice/splice-1.1.0-r2.ebuild b/app-vim/splice/splice-1.1.0-r2.ebuild
deleted file mode 100644
index 84be23b68c9..00000000000
--- a/app-vim/splice/splice-1.1.0-r2.ebuild
+++ /dev/null
@@ -1,35 +0,0 @@
-# Copyright 1999-2020 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-PYTHON_COMPAT=( python2_7 )
-
-inherit vim-plugin python-single-r1 vcs-snapshot
-
-DESCRIPTION="vim plugin: resolve conflicts during three-way merges"
-HOMEPAGE="https://bitbucket.org/sjl/splice.vim/ https://www.vim.org/scripts/script.php?script_id=4026"
-SRC_URI="https://bitbucket.org/sjl/${PN}.vim/get/v${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="MIT"
-KEYWORDS="amd64 x86"
-REQUIRED_USE="${PYTHON_REQUIRED_USE}"
-
-RDEPEND="
- ${PYTHON_DEPS}
- || (
- app-editors/vim[python,${PYTHON_SINGLE_USEDEP}]
- app-editors/gvim[python,${PYTHON_SINGLE_USEDEP}]
- )"
-
-VIM_PLUGIN_HELPFILES="${PN}.txt"
-
-src_prepare() {
- default
- rm .[a-z]* Makefile LICENSE.markdown package.sh || die
- rm -r site || die
-}
-
-src_install() {
- vim-plugin_src_install
- python_optimize "${ED}"/usr/share/vim/vimfiles/autoload/splicelib
-}
diff --git a/app-vim/splice/splice-1.1.0-r3.ebuild b/app-vim/splice/splice-1.1.0-r3.ebuild
index 3593b4bec5f..aea29ebb3e0 100644
--- a/app-vim/splice/splice-1.1.0-r3.ebuild
+++ b/app-vim/splice/splice-1.1.0-r3.ebuild
@@ -11,7 +11,7 @@ HOMEPAGE="https://docs.stevelosh.com/splice.vim/ https://www.vim.org/scripts/scr
SRC_URI="https://bitbucket.org/sjl/${PN}.vim/get/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="MIT"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 x86"
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
RDEPEND="
next reply other threads:[~2020-04-04 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 12:15 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-15 18:39 [gentoo-commits] repo/gentoo:master commit in: app-vim/splice/ Arthur Zamarin
2022-06-10 18:08 Matt Turner
2021-06-01 6:59 Agostino Sarubbo
2021-06-01 6:32 Agostino Sarubbo
2021-05-24 18:52 Michał Górny
2021-03-21 19:50 Patrice Clement
2020-02-09 16:18 Michał Górny
2020-01-13 2:57 Tim Harder
2019-12-13 8:31 Patrice Clement
2019-12-13 8:31 Patrice Clement
2019-06-18 0:35 Aaron Bauman
2017-05-27 15:19 Michał Górny
2017-04-21 7:33 David Seifert
2016-10-31 4:45 Tim Harder
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=1586002542.7c84463c18f4118b175584c993a59e1e9a372ae9.zlogene@gentoo \
--to=zlogene@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