From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] podman: install rootlessport command
Date: Fri, 11 Mar 2022 19:45:16 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36100@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
There is a new pull request by CameronNemo against master on the void-packages repository
https://github.com/CameronNemo/void-packages podman
https://github.com/void-linux/void-packages/pull/36100
podman: install rootlessport command
See #36095 for report
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/36100.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-podman-36100.patch --]
[-- Type: text/x-diff, Size: 1315 bytes --]
From d9bcd87baf857a1b92902e1fc680464ab81464b5 Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Fri, 11 Mar 2022 10:44:13 -0800
Subject: [PATCH] podman: install rootlessport command
See #36095 for report
---
srcpkgs/podman/template | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/podman/template b/srcpkgs/podman/template
index e83467c87f7c..dc06a762c8c4 100644
--- a/srcpkgs/podman/template
+++ b/srcpkgs/podman/template
@@ -1,10 +1,10 @@
# Template file for 'podman'
pkgname=podman
version=4.0.2
-revision=1
+revision=2
build_style=go
go_import_path="github.com/containers/podman/v4"
-go_package="${go_import_path}/cmd/podman"
+go_package="${go_import_path}/cmd/podman ${go_import_path}/cmd/rootlessport"
go_build_tags="seccomp apparmor containers_image_ostree_stub"
hostmakedepends="pkg-config go-md2man"
makedepends="gpgme-devel libseccomp-devel device-mapper-devel libbtrfs-devel"
@@ -26,6 +26,8 @@ post_build() {
}
post_install() {
+ vmkdir usr/libexec/podman
+ mv "${DESTDIR}/usr/bin/rootlessport" "${DESTDIR}/usr/libexec/podman/rootlessport"
make install.man DESTDIR="${DESTDIR}" PREFIX="/usr"
sed -e 's|# cgroup_manager = "systemd"|cgroup_manager = "cgroupfs"|g' \
vendor/github.com/containers/common/pkg/config/containers.conf \
next reply other threads:[~2022-03-11 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 18:45 CameronNemo [this message]
2022-03-11 18:50 ` [PR PATCH] [Updated] " CameronNemo
2022-03-11 21:27 ` podman: install rootlessport and completions lemmi
2022-03-11 21:27 ` [PR PATCH] [Merged]: " lemmi
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-36100@inbox.vuxu.org \
--to=cameronnemo@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).