From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: abiword: update to 3.0.5
Date: Tue, 21 Sep 2021 20:51:02 +0200 [thread overview]
Message-ID: <20210921185102.yvsgiMO-qraH2ZQu2XDZhdzdtFqL9B97qACrIr6SANA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33008@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
There's a merged pull request on the void-packages repository
abiword: update to 3.0.5
https://github.com/void-linux/void-packages/pull/33008
Description:
<!-- 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.
prev parent reply other threads:[~2021-09-21 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 2:04 [PR PATCH] " mtboehlke
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 ` Johnnynator [this message]
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=20210921185102.yvsgiMO-qraH2ZQu2XDZhdzdtFqL9B97qACrIr6SANA@z \
--to=johnnynator@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).