From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] limine: update to 4.20230315.0.
Date: Wed, 15 Mar 2023 10:32:30 +0100 [thread overview]
Message-ID: <20230315093230.2vSlduOaucd-LqLJaPitg6Pg1YNja5W5D6AVGk2oAho@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42750@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/42750
limine: update to 4.20230315.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/42750.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-limine-42750.patch --]
[-- Type: text/x-diff, Size: 1288 bytes --]
From 95bcf3b1f3cbcd2be36c2f985d8107e8e3882825 Mon Sep 17 00:00:00 2001
From: mintsuki <mintsuki@protonmail.com>
Date: Wed, 15 Mar 2023 10:32:22 +0100
Subject: [PATCH] limine: update to 4.20230315.0.
---
srcpkgs/limine/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/limine/template b/srcpkgs/limine/template
index 96c9ab8d9ad3..4322c0250f4c 100644
--- a/srcpkgs/limine/template
+++ b/srcpkgs/limine/template
@@ -1,19 +1,19 @@
# Template file for 'limine'
pkgname=limine
-version=4.20230308.0
+version=4.20230315.0
revision=1
build_style=gnu-configure
-configure_args="--enable-all CROSS_TOOLCHAIN=llvm"
+configure_args="--enable-all FREESTANDING_TOOLCHAIN=llvm"
hostmakedepends="mtools nasm llvm clang lld"
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=dde3c4ecfba7f060e1f35a7f3cd7a04f44f401e97546262c777658df945522aa
+checksum=79a7f12c6a415d455095730ff4eac3d9b08398b508c87782e7d0e5292a0ef729
post_install() {
- vlicense LICENSE.md
+ vlicense LICENSE
}
limine-devel_package() {
next prev parent reply other threads:[~2023-03-15 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 21:08 [PR PATCH] limine: update to 4.20230313.0 mintsuki
2023-03-14 20:31 ` [PR PATCH] [Updated] limine: update to 4.20230314.0 mintsuki
2023-03-15 9:32 ` mintsuki [this message]
2023-03-15 17:32 ` [PR PATCH] [Merged]: limine: update to 4.20230315.0 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=20230315093230.2vSlduOaucd-LqLJaPitg6Pg1YNja5W5D6AVGk2oAho@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).