From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] doxygen: update to 1.12.0.
Date: Fri, 10 Jan 2025 11:06:15 +0100 [thread overview]
Message-ID: <20250110100615.504F622DB8@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53680@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
There is an updated pull request by meator against master on the void-packages repository
https://github.com/meator/void-packages doxygen-1.12
https://github.com/void-linux/void-packages/pull/53680
doxygen: update to 1.12.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES** (I'm actively using it in my project)
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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
-->
A patch file from https://github.com/void-linux/void-packages/pull/53680.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-doxygen-1.12-53680.patch --]
[-- Type: text/x-diff, Size: 1058 bytes --]
From b9687fcf4eda30eea23aae025972bb1643743d15 Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Wed, 25 Dec 2024 19:08:49 +0100
Subject: [PATCH] doxygen: update to 1.13.2.
---
srcpkgs/doxygen/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/doxygen/template b/srcpkgs/doxygen/template
index fbc8d6b951873b..135f5ed0cfada6 100644
--- a/srcpkgs/doxygen/template
+++ b/srcpkgs/doxygen/template
@@ -1,6 +1,6 @@
# Template file for 'doxygen'
pkgname=doxygen
-version=1.9.8
+version=1.13.2
revision=1
build_style=cmake
hostmakedepends="perl python3 flex"
@@ -11,7 +11,7 @@ license="GPL-2.0-only"
homepage="http://www.doxygen.org/"
changelog="https://www.doxygen.nl/manual/changelog.html"
distfiles="http://doxygen.nl/files/doxygen-${version}.src.tar.gz"
-checksum=05e3d228e8384b5f3af9c8fd6246d22804acb731a3a24ce285c8986ed7e14f62
+checksum=3a25e3386c26ea5494c784e946327225debfbc5dbfa8b13549010a315aace66d
build_options="wizard"
desc_option_wizard="build Qt5 GUI configuration tool, doxywizard"
prev parent reply other threads:[~2025-01-10 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 18:09 [PR PATCH] " meator
2025-01-10 10:04 ` [PR PATCH] [Updated] " meator
2025-01-10 10:06 ` meator [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=20250110100615.504F622DB8@inbox.vuxu.org \
--to=meator@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).