From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] aspell: split tools into a subpkg
Date: Mon, 26 Oct 2020 04:49:12 +0100 [thread overview]
Message-ID: <20201026034912.QGZzE6dpFfWyhI0156dz7N3ut87YRsNWdnLZ9PzWGkU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25648@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
There is an updated pull request by CameronNemo against master on the void-packages repository
https://github.com/CameronNemo/void-packages aspell
https://github.com/void-linux/void-packages/pull/25648
aspell: split tools into a subpkg
None
A patch file from https://github.com/void-linux/void-packages/pull/25648.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-aspell-25648.patch --]
[-- Type: text/x-diff, Size: 1820 bytes --]
From 6a7a3c58e845855f6aa3098918bfc0638992a30d Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Thu, 15 Oct 2020 21:42:39 -0700
Subject: [PATCH] aspell: split library into a subpkg
---
common/shlibs | 4 ++--
srcpkgs/aspell/template | 10 +++++++++-
srcpkgs/libaspell | 1 +
3 files changed, 12 insertions(+), 3 deletions(-)
create mode 120000 srcpkgs/libaspell
diff --git a/common/shlibs b/common/shlibs
index 856f9de9a6e..aae34d15456 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -554,8 +554,8 @@ libicudata.so.67 icu-libs-67.1_1
libicutu.so.67 icu-libs-67.1_1
libicuuc.so.67 icu-libs-67.1_1
libicutest.so.67 icu-libs-67.1_1
-libaspell.so.15 aspell-0.60_1
-libpspell.so.15 aspell-0.60_1
+libaspell.so.15 libaspell-0.60.8_2
+libpspell.so.15 libaspell-0.60.8_2
libenchant.so.1 enchant-1.4.2_1
libenchant-2.so.2 enchant2-2.2.3_1
libgconf-2.so.4 GConf-2.32.0_1
diff --git a/srcpkgs/aspell/template b/srcpkgs/aspell/template
index b3ccbeeaef8..414e0adedfd 100644
--- a/srcpkgs/aspell/template
+++ b/srcpkgs/aspell/template
@@ -1,7 +1,7 @@
# Template file for 'aspell'
pkgname=aspell
version=0.60.8
-revision=1
+revision=2
build_style=gnu-configure
configure_args="--enable-compile-in-filters"
hostmakedepends="automake libtool gettext-devel perl"
@@ -22,6 +22,14 @@ pre_configure() {
autoreconf -fi
}
+libaspell_package() {
+ short_desc+=" - library"
+ pkg_install() {
+ vmove "usr/lib/*.so.*"
+ vmove "usr/lib/aspell-*"
+ }
+}
+
aspell-devel_package() {
depends="ncurses-devel libstdc++-devel aspell>=${version}_${revision}"
short_desc+=" - development files"
diff --git a/srcpkgs/libaspell b/srcpkgs/libaspell
new file mode 120000
index 00000000000..2954cad5043
--- /dev/null
+++ b/srcpkgs/libaspell
@@ -0,0 +1 @@
+aspell
\ No newline at end of file
next prev parent reply other threads:[~2020-10-26 3:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 4:43 [PR PATCH] " CameronNemo
2020-10-17 2:46 ` ericonr
2020-10-18 2:35 ` CameronNemo
2020-10-18 2:35 ` CameronNemo
2020-10-18 14:41 ` sgn
2020-10-18 22:33 ` Duncaen
2020-10-25 6:57 ` sgn
2020-10-26 3:14 ` [PR PATCH] [Updated] " CameronNemo
2020-10-26 3:49 ` CameronNemo [this message]
2020-10-26 4:09 ` CameronNemo
2020-10-26 11:43 ` [PR REVIEW] aspell: split library " Duncaen
2020-10-26 17:04 ` CameronNemo
2020-10-26 17:16 ` Duncaen
2020-11-06 2:23 ` [PR PATCH] [Merged]: " abenson
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=20201026034912.QGZzE6dpFfWyhI0156dz7N3ut87YRsNWdnLZ9PzWGkU@z \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).