From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: cups: update to 2.4.1.
Date: Sun, 20 Mar 2022 22:28:38 +0100 [thread overview]
Message-ID: <20220320212838.QvgtRaHdZCWHcBoex3-HPOBmxeGkp0vf-qqkxwdQkgc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33939@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
There's a closed pull request on the void-packages repository
cups: update to 2.4.1.
https://github.com/void-linux/void-packages/pull/33939
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
-->
This is in preparation for the upcoming cups 2.4 release. Lots of configure flags became redundant, got sane defaults or just straight up changed, so I cleaned those up quite a bit. Some of the post_install actions are also no longer required.
Compression support is now enabled with the zlib-devel makedepend, which should speed things up with IPP printers that support it.
Testing is very much welcome.
prev parent reply other threads:[~2022-03-20 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 13:42 [PR PATCH] [WIP] cups: update to 2.4b1 oynqr
2021-11-12 6:58 ` [PR PATCH] [Updated] " oynqr
2021-11-12 6:59 ` [PR PATCH] [Updated] [WIP] cups: update to 2.4rc1 oynqr
2021-11-12 7:21 ` oynqr
2021-11-30 11:13 ` [PR PATCH] [Updated] " oynqr
2022-01-30 11:01 ` [PR PATCH] [Updated] cups: update to 2.4.0 oynqr
2022-03-20 21:28 ` Piraty [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=20220320212838.QvgtRaHdZCWHcBoex3-HPOBmxeGkp0vf-qqkxwdQkgc@z \
--to=piraty@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).