From: mtboehlke <mtboehlke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] abiword: update to 3.0.5
Date: Sat, 18 Sep 2021 04:04:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33008@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]
There is a new pull request by mtboehlke against master on the void-packages repository
https://github.com/mtboehlke/void-packages abiword
https://github.com/void-linux/void-packages/pull/33008
abiword: update to 3.0.5
Remove unnecessary configure flags and make champlain a build option
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
Configure flags --enable-goffice and --with-gtk3 are shown as unrecognized and not needed.
`libchamplain` pulls in clutter, which is kind of a bit much considering that, IMHO, the appeal of Abiword is that it doesn't come with the baggage of a complete office suite, so I made it a build option, enabled for now in the case that there are those who use the functionality.
A patch file from https://github.com/void-linux/void-packages/pull/33008.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-abiword-33008.patch --]
[-- Type: text/x-diff, Size: 1861 bytes --]
From ccaddd31f2a2cbfd2f03a4b2bf43f27b3d496b59 Mon Sep 17 00:00:00 2001
From: Mat Boehlke <mtboehlke@gmail.com>
Date: Fri, 17 Sep 2021 20:44:05 -0500
Subject: [PATCH] abiword: update to 3.0.5
Remove unnecessary configure flags and make champlain a build option
---
srcpkgs/abiword/template | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/srcpkgs/abiword/template b/srcpkgs/abiword/template
index 782d023e01dc..9dc643e5c05d 100644
--- a/srcpkgs/abiword/template
+++ b/srcpkgs/abiword/template
@@ -1,14 +1,13 @@
# Template file for 'abiword'
pkgname=abiword
-version=3.0.4
-revision=2
+version=3.0.5
+revision=1
build_style=gnu-configure
-configure_args="--enable-plugins --enable-clipart --enable-templates
- --with-gtk3 $(vopt_enable goffice)"
+configure_args="--enable-plugins --enable-clipart --enable-templates"
hostmakedepends="automake libtool flex pkg-config"
makedepends="libjpeg-turbo-devel libpng-devel fribidi-devel libgsf-devel
enchant2-devel librsvg-devel wv-devel boost-devel libxslt-devel
- libwmf-devel libchamplain-devel redland-devel libical-devel
+ libwmf-devel $(vopt_if champlain libchamplain-devel) redland-devel libical-devel
libgcrypt-devel harfbuzz-devel $(vopt_if goffice goffice-devel)
gtk+3-devel"
depends="hicolor-icon-theme desktop-file-utils"
@@ -17,10 +16,10 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later"
homepage="http://www.abisource.com/"
distfiles="${homepage}/downloads/${pkgname}/${version}/source/${pkgname}-${version}.tar.gz"
-checksum=e93096cb192e5bc19d62e180fc5eda643206465315a710113ae5036bc2a1a5d7
+checksum=1257247e9970508d6d1456d3e330cd1909c4b42b25e0f0a1bc32526d6f3a21b4
-build_options="goffice"
-build_options_default="goffice"
+build_options="goffice champlain"
+build_options_default="goffice champlain"
CXXFLAGS="-std=c++11"
next reply other threads:[~2021-09-18 2:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 2:04 mtboehlke [this message]
2021-09-18 4:36 ` mtboehlke
2021-09-18 4:37 ` mtboehlke
2021-09-18 4:38 ` mtboehlke
2021-09-18 12:51 ` [PR PATCH] [Updated] " mtboehlke
2021-09-18 12:53 ` mtboehlke
2021-09-18 12:53 ` mtboehlke
2021-09-18 12:53 ` mtboehlke
2021-09-21 18:51 ` [PR PATCH] [Merged]: " Johnnynator
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33008@inbox.vuxu.org \
--to=mtboehlke@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).