Github messages for voidlinux
 help / color / mirror / Atom feed
From: zenfailure <zenfailure@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: 66-boot-0.1.2.1
Date: Sun, 19 Apr 2020 06:44:21 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21142@inbox.vuxu.org> (raw)

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

There is a new pull request by zenfailure against master on the void-packages repository

https://github.com/zenfailure/void-packages 66-boot
https://github.com/void-linux/void-packages/pull/21142

New package: 66-boot-0.1.2.1
None

A patch file from https://github.com/void-linux/void-packages/pull/21142.patch is attached

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

From 0b2471edff48f5e40cddf1e4f680edc6e281c0fb Mon Sep 17 00:00:00 2001
From: Iskander Zemmouri <iskander.zemmouri@mailbox.org>
Date: Mon, 6 Apr 2020 21:27:17 +0200
Subject: [PATCH] New package: 66-boot-0.1.2.1

---
 srcpkgs/66-boot/INSTALL            | 10 ++++++++++
 srcpkgs/66-boot/INSTALL.msg        |  3 +++
 srcpkgs/66-boot/REMOVE             |  6 ++++++
 srcpkgs/66-boot/files/66-bootstart |  2 ++
 srcpkgs/66-boot/files/tty@         | 12 ++++++++++++
 srcpkgs/66-boot/template           | 24 ++++++++++++++++++++++++
 6 files changed, 57 insertions(+)
 create mode 100644 srcpkgs/66-boot/INSTALL
 create mode 100644 srcpkgs/66-boot/INSTALL.msg
 create mode 100644 srcpkgs/66-boot/REMOVE
 create mode 100644 srcpkgs/66-boot/files/66-bootstart
 create mode 100644 srcpkgs/66-boot/files/tty@
 create mode 100644 srcpkgs/66-boot/template

diff --git a/srcpkgs/66-boot/INSTALL b/srcpkgs/66-boot/INSTALL
new file mode 100644
index 00000000000..8dcc4ce024c
--- /dev/null
+++ b/srcpkgs/66-boot/INSTALL
@@ -0,0 +1,10 @@
+if [ "$UPDATE" = "no" ]; then
+	case "${ACTION}" in
+	post)
+		66-tree -n boot
+		66-enable -t boot boot
+		66-tree -ncE default
+		66-enable -t default tty@tty1 tty@tty2 tty@tty3 tty@tty4
+		;;
+	esac
+fi
diff --git a/srcpkgs/66-boot/INSTALL.msg b/srcpkgs/66-boot/INSTALL.msg
new file mode 100644
index 00000000000..d07c97363db
--- /dev/null
+++ b/srcpkgs/66-boot/INSTALL.msg
@@ -0,0 +1,3 @@
+To boot with 66, simply add the argument `init=/usr/bin/66-bootstart' to your kernel commandline.
+
+The available service files are packaged in `66-services'.
diff --git a/srcpkgs/66-boot/REMOVE b/srcpkgs/66-boot/REMOVE
new file mode 100644
index 00000000000..9dc0c4270ba
--- /dev/null
+++ b/srcpkgs/66-boot/REMOVE
@@ -0,0 +1,6 @@
+case "${ACTION}" in
+	post)
+		66-tree -R boot
+		66-tree -R default
+		;;
+esac
diff --git a/srcpkgs/66-boot/files/66-bootstart b/srcpkgs/66-boot/files/66-bootstart
new file mode 100644
index 00000000000..81d37211783
--- /dev/null
+++ b/srcpkgs/66-boot/files/66-bootstart
@@ -0,0 +1,2 @@
+#!/usr/bin/execlineb -P
+66-boot -b "Booting with 66-boot..." -m /run
diff --git a/srcpkgs/66-boot/files/tty@ b/srcpkgs/66-boot/files/tty@
new file mode 100644
index 00000000000..dcb2671922f
--- /dev/null
+++ b/srcpkgs/66-boot/files/tty@
@@ -0,0 +1,12 @@
+[main]
+@type = classic
+@description = "Launch @I"
+@user = ( root )
+@options = ( env )
+
+[start]
+@build = auto
+@execute = ( execl-cmdline -s { agetty ${cmd_args} @I } )
+
+[environment]
+cmd_args=!-J 38400
diff --git a/srcpkgs/66-boot/template b/srcpkgs/66-boot/template
new file mode 100644
index 00000000000..be3fcf90b76
--- /dev/null
+++ b/srcpkgs/66-boot/template
@@ -0,0 +1,24 @@
+# Template file for '66-boot'
+pkgname=66-boot
+_realpkgname=boot-66serv
+version=0.1.2.1
+revision=1
+archs="noarch"
+wrksrc=${_realpkgname}-v${version}
+build_style=gnu-configure
+makedepends="file"
+depends="66 s6-rc 66-tools s6-linux-utils"
+short_desc="Stage 1 boot for 66"
+maintainer="Iskander Zemmouri <iskander.zemmouri@mailbox.org>"
+license="ISC"
+homepage="https://framagit.org/Obarun/boot-66serv"
+distfiles="https://framagit.org/Obarun/${_realpkgname}/-/archive/v${version}/${_realpkgname}-v${version}.tar.gz"
+checksum=508fb91de713664ba5244f5d50a9cde106ce03be63dad24e03bfa813f40af2ea
+conf_files="/etc/66/*.conf
+ /etc/66/rc.local"
+
+post_install() {
+	vinstall ${FILESDIR}/tty@ 644 usr/share/66/service/
+	vinstall ${FILESDIR}/66-bootstart 755 usr/bin
+	vlicense LICENSE
+}

             reply	other threads:[~2020-04-19  4:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  4:44 zenfailure [this message]
2020-04-19 12:08 ` [PR PATCH] [Updated] " zenfailure
2020-04-20  5:11 ` zenfailure
2020-12-20  1:49 ` ericonr
2021-02-16  6:00 ` ericonr
2021-02-16  6:00 ` [PR PATCH] [Closed]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21142@inbox.vuxu.org \
    --to=zenfailure@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).