From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] limine: update to 4.20230227.0.
Date: Mon, 27 Feb 2023 02:15:59 +0100 [thread overview]
Message-ID: <20230227011559.CClGEFxkEAOa_rSIIZXayo3gIlFO31sGNucnqnCsGUM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42321@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
There is an updated pull request by mintsuki against master on the void-packages repository
https://github.com/mintsuki/void-packages limine
https://github.com/void-linux/void-packages/pull/42321
limine: update to 4.20230227.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/42321.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-limine-42321.patch --]
[-- Type: text/x-diff, Size: 1232 bytes --]
From 0217eeeba0d6ccfd66d22f5cc0e2a25344c9cd45 Mon Sep 17 00:00:00 2001
From: mintsuki <mintsuki@protonmail.com>
Date: Mon, 27 Feb 2023 02:15:53 +0100
Subject: [PATCH] limine: update to 4.20230227.0.
---
srcpkgs/limine/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/limine/template b/srcpkgs/limine/template
index c943049d3515..cdcc4f0c9d9c 100644
--- a/srcpkgs/limine/template
+++ b/srcpkgs/limine/template
@@ -1,16 +1,16 @@
# Template file for 'limine'
pkgname=limine
-version=4.20230215.0
+version=4.20230227.0
revision=1
build_style=gnu-configure
configure_args="--enable-all CROSS_TOOLCHAIN=llvm"
hostmakedepends="mtools nasm llvm clang lld"
-short_desc="Advanced x86/x86_64 BIOS/UEFI bootloader"
+short_desc="Advanced, portable, multiprotocol bootloader"
maintainer="Mintsuki <mintsuki@protonmail.com>"
license="BSD-2-Clause"
homepage="https://limine-bootloader.org/"
distfiles="https://github.com/limine-bootloader/limine/releases/download/v${version}/limine-${version}.tar.xz"
-checksum=e2cf926937c276b029488eec26053d4797be75eed67cbc8429680ae9487a9a3c
+checksum=484009065d3ee70dc608376bf3b096760cf062d756b47c3070927bfaca534765
post_install() {
vlicense LICENSE.md
next prev parent reply other threads:[~2023-02-27 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 22:30 [PR PATCH] limine: update to 4.20230216.1 mintsuki
2023-02-19 10:02 ` [PR PATCH] [Updated] " mintsuki
2023-02-21 2:55 ` [PR PATCH] [Updated] limine: update to 4.20230221.0 mintsuki
2023-02-27 1:15 ` mintsuki [this message]
2023-03-05 10:29 ` [PR PATCH] [Updated] limine: update to 4.20230227.0 mintsuki
2023-03-06 2:33 ` [PR PATCH] [Updated] limine: update to 4.20230305.2 mintsuki
2023-03-07 13:23 ` [PR PATCH] [Updated] limine: update to 4.20230307.0 mintsuki
2023-03-08 17:27 ` [PR PATCH] [Updated] limine: update to 4.20230308.0 mintsuki
2023-03-11 7:34 ` [PR PATCH] [Merged]: " classabbyamp
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=20230227011559.CClGEFxkEAOa_rSIIZXayo3gIlFO31sGNucnqnCsGUM@z \
--to=mintsuki@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).