Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45323 - [networkmanager-qt] Dependency simplicfication.

Attached to Project: Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Saturday, 13 June 2015, 22:04 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 14 June 2015, 00:17 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Right networkmanager-qt depends on full networkmanager package but since it is pretty much just a Qt wrapper around libnm-glib package (only apps using networmanager-qt actually need the full networkmanager package).

1. Make networkmanager-qt depend ONLY on libnm-glib (it doesn't really need the whole networkmanager package).
2. Make frontends to networkmanager-qt such as plasma-nm require networkmanager-qt and networkmanager.
3. Change plasma-workspace to fully depend on networkmanager-qt but optionally depend on the full networkmanager package.

This heavily reduces the dependencies of networkmanager-qt.
Thank you.
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 14 June 2015, 00:17 GMT
Reason for closing:  Not a bug
Additional comments about closing:  nm-qt is requires the d-bus api in networkmanager
Comment by Antonio Rojas (arojas) - Sunday, 14 June 2015, 00:05 GMT
I don't see the point of this. What is the use case for installing networkmanager-qt but not installing networkmanager? Why would you install networkmanager-qt if you're not going to use a frontend for it?

Also note that networkmanager-qt is a wrapper for the NM dbus API, it doesn't link to libnm-glib at all.
Comment by Hussam Al-Tayeb (hussam) - Sunday, 14 June 2015, 00:13 GMT
For starters, a smaller output file when running lddd (less on-disk broken dependencies).
But it's just a suggestion :) If there's not point for it, then it's not necessary :)

It's kinda like how many things link against libpulse but don't necessarily depend on pulseaudio package.

To answer your question, what is the use case of someone wanting to have libpulse installed but not pulseaudio?

Loading...