From: ltrsunny <ltrsunny@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Change default runtime to crun
Date: Mon, 27 Jun 2022 13:57:42 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37706@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
There is a new pull request by ltrsunny against master on the void-packages repository
https://github.com/ltrsunny/void-packages patch-1
https://github.com/void-linux/void-packages/pull/37706
Change default runtime to crun
crun is a more lighter and popular choice now.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
<!--
#### 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 add ci skip tag as described in
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/37706.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-37706.patch --]
[-- Type: text/x-diff, Size: 1080 bytes --]
From 8b0fada9581d93da21211d5eb29f657f498ffe70 Mon Sep 17 00:00:00 2001
From: Liu Taoran <49466661+ltrsunny@users.noreply.github.com>
Date: Mon, 27 Jun 2022 19:57:12 +0800
Subject: [PATCH] Change default runtime to crun
crun is a more lighter and popular choice now.
---
srcpkgs/podman/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/podman/template b/srcpkgs/podman/template
index bc2e8cce46cb..b75bf1bf52ce 100644
--- a/srcpkgs/podman/template
+++ b/srcpkgs/podman/template
@@ -8,7 +8,7 @@ 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"
-depends="runc conmon cni-plugins slirp4netns containers.image fuse-overlayfs"
+depends="crun conmon cni-plugins slirp4netns containers.image fuse-overlayfs"
short_desc="Simple management tool for containers and images"
maintainer="Cameron Nemo <cnemo@tutanota.com>"
license="Apache-2.0"
next reply other threads:[~2022-06-27 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 11:57 ltrsunny [this message]
2022-06-27 12:56 ` ahesford
2022-06-27 12:56 ` ahesford
2022-06-27 14:16 ` ltrsunny
2022-06-27 16:03 ` CameronNemo
2022-06-27 16:06 ` CameronNemo
2022-06-27 19:18 ` ahesford
2022-09-29 2:14 ` Podman: change " github-actions
2022-10-13 2:15 ` [PR PATCH] [Closed]: " github-actions
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-37706@inbox.vuxu.org \
--to=ltrsunny@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).