From: phikal <phikal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] base-system: Removed wifi dependencies
Date: Sun, 26 Apr 2020 15:47:45 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21351@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
There is a new pull request by phikal against master on the void-packages repository
https://github.com/phikal/void-packages-1 master
https://github.com/void-linux/void-packages/pull/21351
base-system: Removed wifi dependencies
I use void on a Raspberry Pi, and it doesn't have WiFi. When trimming the system down to what I need, I always get stuck on a view `base-system` dependencies that would like to remove without using XBPS `-f` flag.
Here I suggest dropping the WiFi related packages, but would more generally like to start a conversation about dropping others too (`void-artwork`, `btrfs-progs`, `xfsprogs`, ...).
I'm not familiar enough with the void system at large to know what the consequences would be. Just ignore and close this pull request if I'm opening some Pandora's box, that should just be ignored.
A patch file from https://github.com/void-linux/void-packages/pull/21351.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-21351.patch --]
[-- Type: text/x-diff, Size: 1013 bytes --]
From 4b2679a5ba3f37b43ad6e67ff3474e0459ab5845 Mon Sep 17 00:00:00 2001
From: Philip K <philip@warpmail.net>
Date: Sun, 26 Apr 2020 15:34:34 +0200
Subject: [PATCH] base-system: Removed wifi dependencies
---
srcpkgs/base-system/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/base-system/template b/srcpkgs/base-system/template
index 810563c1bad..cd22c36380b 100644
--- a/srcpkgs/base-system/template
+++ b/srcpkgs/base-system/template
@@ -13,8 +13,8 @@ depends="
dash bash grep gzip file sed gawk less util-linux which tar man-pages
mdocml>=1.13.3 shadow e2fsprogs btrfs-progs xfsprogs f2fs-tools dosfstools
procps-ng tzdata pciutils usbutils iana-etc openssh dhcpcd
- kbd iproute2 iputils iw wpa_supplicant xbps nvi sudo wifi-firmware
- void-artwork traceroute ethtool kmod acpid eudev runit-void"
+ kbd iproute2 iputils iw xbps nvi sudo void-artwork traceroute
+ ethtool kmod acpid eudev runit-void"
case "$XBPS_TARGET_MACHINE" in
*-musl) depends+=" musl";;
next reply other threads:[~2020-04-26 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 13:47 phikal [this message]
2020-04-26 15:51 ` Duncaen
2020-04-26 15:51 ` [PR PATCH] [Closed]: " Duncaen
2020-04-26 16:39 ` NeelChotai
2020-04-26 17:51 ` Piraty
2020-04-26 18:24 ` phikal
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-21351@inbox.vuxu.org \
--to=phikal@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).