Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] util-linux: compile with eudev
Date: Wed, 30 Oct 2019 05:16:40 +0100	[thread overview]
Message-ID: <20191030041640.ZCAntycJnU05eq68Yu0E2acvchbbrzQ0_cz8HjxUi8Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15920@inbox.vuxu.org>

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

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

https://github.com/zdtcd/void-packages util-linux-udev
https://github.com/void-linux/void-packages/pull/15920

util-linux: compile with eudev
lsblk needs udev support to read LABEL, UUID and filesystem without root
permission.

eudev is already a dependency of base-voidstrap and base-system,
so most of people won't be effected by this new dependencies.

However, base-minimal depends on util-linux but not eudev.

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-util-linux-udev-15920.patch --]
[-- Type: text/x-diff, Size: 1608 bytes --]

From 5e819934b50f99dc826b1b7558867d2e93e8cad7 Mon Sep 17 00:00:00 2001
From: Doan Tran Cong Danh <congdanhqx@gmail.com>
Date: Wed, 30 Oct 2019 08:24:20 +0700
Subject: [PATCH] util-linux: compile with eudev

lsblk needs udev support to read LABEL, UUID and filesystem without root
permission.

eudev is already a dependency of base-voidstrap and base-system,
so most of people won't be effected by this new dependencies.

However, base-minimal depends on util-linux but not eudev.
---
 srcpkgs/util-linux/template | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/util-linux/template b/srcpkgs/util-linux/template
index 9f912097d85..99cc99f8e16 100644
--- a/srcpkgs/util-linux/template
+++ b/srcpkgs/util-linux/template
@@ -1,9 +1,9 @@
 # Template file for 'util-linux'
 pkgname=util-linux
 version=2.34
-revision=2
+revision=3
 hostmakedepends="automake bison gettext-devel libtool pkg-config"
-makedepends="libcap-ng-devel pam-devel readline-devel zlib-devel"
+makedepends="libcap-ng-devel pam-devel readline-devel zlib-devel eudev-libudev-devel"
 checkdepends="ncurses" # Some tests require terminfo-entries
 short_desc="Miscellaneous linux utilities"
 maintainer="Enno Boland <gottox@voidlinux.org>"
@@ -40,8 +40,7 @@ do_configure() {
 		--enable-fs-paths-extra=/usr/sbin:/usr/bin \
 		--enable-vipw --enable-newgrp --enable-chfn-chsh \
 		--with-systemdsystemunitdir=no \
-		--without-udev --without-python \
-		--enable-write
+		--without-python --enable-write
 }
 
 do_build() {
@@ -152,4 +151,3 @@ libsmartcols_package() {
 		vmove usr/lib/libsmartcols.so.*
 	}
 }
-

  reply	other threads:[~2019-10-30  4:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  1:32 [PR PATCH] " voidlinux-github
2019-10-30  4:16 ` voidlinux-github [this message]
2019-10-30  4:16 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-02  9:36 ` [PR PATCH] [Merged]: " voidlinux-github
2019-11-08 22:05 ` voidlinux-github
2019-11-08 22:05 ` voidlinux-github
2019-11-08 22:06 ` voidlinux-github
2019-11-08 22:39 ` voidlinux-github

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=20191030041640.ZCAntycJnU05eq68Yu0E2acvchbbrzQ0_cz8HjxUi8Y@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).