Github messages for voidlinux
 help / color / mirror / Atom feed
From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: limine-2.24
Date: Sat, 26 Jun 2021 13:38:30 +0200	[thread overview]
Message-ID: <20210626113830.HtcPsS7HXhyK3EE6zYFAOMoOzIH14Nqe0EwTeWJsU4Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31658@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]

There is an updated pull request by mintsuki against master on the void-packages repository

https://github.com/mintsuki-org/void-packages master
https://github.com/void-linux/void-packages/pull/31658

New package: limine-2.24
<!-- Mark items with [x] where applicable -->

#### General
- [x] 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.)
- [x] 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/31658.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-31658.patch --]
[-- Type: text/x-diff, Size: 1475 bytes --]

From f0f74b0c31b6ebbaa182bc9da454261c6fdfbf60 Mon Sep 17 00:00:00 2001
From: mintsuki <mintsuki@protonmail.com>
Date: Sat, 26 Jun 2021 13:38:25 +0200
Subject: [PATCH] New package: limine-2.24

---
 srcpkgs/limine/template | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 srcpkgs/limine/template

diff --git a/srcpkgs/limine/template b/srcpkgs/limine/template
new file mode 100644
index 000000000000..e18fac5caece
--- /dev/null
+++ b/srcpkgs/limine/template
@@ -0,0 +1,37 @@
+# Template file for 'limine'
+pkgname=limine
+version=2.24
+revision=1
+archs="x86_64"
+hostmakedepends="which nasm mtools git"
+short_desc="Advanced x86/x86_64 BIOS and UEFI bootloader"
+maintainer="mintsuki <mintsuki@protonmail.com>"
+license="BSD-2-Clause"
+homepage="https://limine-bootloader.org"
+checksum=8e1dc14b097485c4a36107f701bbd75f27d919a818a01ebe26e82cb2fd0d9172
+
+do_fetch() {
+	git clone --depth=1 --branch=v$version https://github.com/limine-bootloader/limine.git limine-$version
+}
+
+# This is necessary because stock /etc/mtools.conf may contain a syntax error that makes mtools fail.
+pre_build() {
+	vsed -i /etc/mtools.conf -e 's/SAMPLE FILE/#### SAMPLE FILE/g'
+}
+
+do_build() {
+	make
+}
+
+# Restore original /etc/mtools.conf
+post_build() {
+	vsed -i /etc/mtools.conf -e 's/#### SAMPLE FILE/SAMPLE FILE/g'
+}
+
+do_install() {
+	make install PREFIX="/usr" DESTDIR="$DESTDIR"
+}
+
+post_install() {
+	vlicense LICENSE.md
+}

  parent reply	other threads:[~2021-06-26 11:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 22:21 [PR PATCH] " mintsuki
2021-06-26  6:34 ` Anachron
2021-06-26 11:38 ` mintsuki [this message]
2021-06-26 11:51 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 11:55 ` mintsuki
2021-06-26 11:55 ` [PR REVIEW] " Johnnynator
2021-06-26 11:55 ` Johnnynator
2021-06-26 11:57 ` mintsuki
2021-06-26 11:57 ` Johnnynator
2021-06-26 11:57 ` mintsuki
2021-06-26 11:58 ` [PR REVIEW] " Johnnynator
2021-06-26 12:00 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 12:00 ` mintsuki
2021-06-26 12:04 ` [PR REVIEW] " mintsuki
2021-06-26 12:05 ` mintsuki
2021-06-26 12:21 ` mintsuki
2021-06-26 12:21 ` mintsuki
2021-06-26 12:23 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 12:26 ` mintsuki
2021-06-26 12:28 ` mintsuki
2021-06-26 12:31 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 12:34 ` mintsuki
2021-06-26 13:04 ` mintsuki
2021-06-26 13:12 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 13:34 ` mintsuki
2021-06-26 13:44 ` [PR REVIEW] " Johnnynator
2021-06-26 13:44 ` Johnnynator
2021-06-26 13:59 ` mintsuki
2021-06-26 14:02 ` mintsuki
2021-06-26 14:03 ` mintsuki
2021-06-26 14:04 ` mintsuki
2021-06-26 14:05 ` mintsuki
2021-06-26 14:06 ` mintsuki
2021-06-26 14:11 ` [PR REVIEW] " Johnnynator
2021-06-26 14:11 ` Johnnynator
2021-06-26 14:16 ` Johnnynator
2021-06-26 15:02 ` [PR PATCH] [Updated] " mintsuki
2021-06-26 15:06 ` mintsuki
2021-06-26 15:10 ` mintsuki
2021-06-27 19:19 ` [PR REVIEW] " Johnnynator
2021-06-27 19:19 ` Johnnynator
2021-06-27 19:19 ` Johnnynator
2021-06-27 19:45 ` [PR PATCH] [Updated] " mintsuki
2021-06-27 19:49 ` mintsuki
2021-07-11  3:06 ` [PR PATCH] [Closed]: " mintsuki
2021-07-11  3:13 ` ericonr

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=20210626113830.HtcPsS7HXhyK3EE6zYFAOMoOzIH14Nqe0EwTeWJsU4Q@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).