Github messages for voidlinux
 help / color / mirror / Atom feed
From: b1scu1t <b1scu1t@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] dkms: Drop the 'linux-headers' package dependency?
Date: Mon, 17 Feb 2020 04:59:51 +0100	[thread overview]
Message-ID: <20200217035951.GXGctBZ-wj-S307dvBujUACjBiDAIY5qo-WSixh40BY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18976@inbox.vuxu.org>

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

Closed issue by b1scu1t on void-packages repository

https://github.com/void-linux/void-packages/issues/18976

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->

### System

* package:  
`dkms_2.8.1`

### Expected behavior
To be able to install `dkms` without requiring the `linux-headers` meta-package. 

### Actual behavior
The `linux-headers` meta-package is installed, even if kernel headers are already provided by another package. E.g: `linux-lts-headers`.

### Steps to reproduce the behavior
`sudo xbps-install -S dkms`

### Notes
As Void provides multiple kernels and kernel headers, I don't think it would be good to have dkms depend on one package in particular. I only use `linux-lts` and `linux-lts-headers`, but dkms will also generate modules for `linux`, which I don't have installed.


      parent reply	other threads:[~2020-02-17  3:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 14:06 [ISSUE] " voidlinux-github
2020-02-09 14:06 ` [ISSUE] [CLOSED] " voidlinux-github
2020-02-09 16:22 ` voidlinux-github
2020-02-09 16:23 ` voidlinux-github
2020-02-09 16:47 ` voidlinux-github
2020-02-09 16:48 ` voidlinux-github
2020-02-09 17:02 ` voidlinux-github
2020-02-10  6:49 ` voidlinux-github
2020-02-10 12:46 ` voidlinux-github
2020-02-10 15:34 ` voidlinux-github
2020-02-10 18:50 ` voidlinux-github
2020-02-10 18:51 ` voidlinux-github
2020-02-12 12:15 ` voidlinux-github
2020-02-12 13:39 ` voidlinux-github
2020-02-17  3:59 ` b1scu1t
2020-02-17  3:59 ` b1scu1t [this message]

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=20200217035951.GXGctBZ-wj-S307dvBujUACjBiDAIY5qo-WSixh40BY@z \
    --to=b1scu1t@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).