Locking out dependencies?

lgrant

lgrant

Is there any way to mark a dependency so it does not ever get installed?

I am trying really hard to not have PulseAudio installed on my system, and I keep finding unexpected, non-audio-related packages that depend on it, like Blender, FreeCAD, and KImageMapEditor. I always check the list of dependencies to make sure PulseAudio is not there, but since I am not infallible, I was wondering if there was a way to tell pkg not to install anything that required PulseAudio.

Thanks!
 
Package dependencies are pretty much set in stone. There could be various "flavors" that may have different options set, but those dependencies are still hardcoded. And not all ports have or use flavors. The only way to properly enable/disable options you want is to build from ports. And the best way to do that is to use a tool like poudriere or Synth.
 
I would hack up pkg(8). It's worth it.

Obviously I assume that you don't want any of the packages that depend on PA.
 
forums.freebsd.org

Ignoring/Blacklisting packages?

I need to use devel/android-tools-adb to update my smartphones to current LineageOS. This however conflicts with poetteringware (avahi) that gets installed by the KDE metapackage but is not being used by me (the KDE stuff that "depends" on avahi runs fine without it). It complains that...
forums.freebsd.org forums.freebsd.org

adorno said:
… a write-up by [FONT=monospace]dvl@[/FONT] …
Click to expand...

Cath O'Deray said:
… <https://forums.freebsd.org/posts/528187> was my record of creating a fake manifest.

(It's no longer required; KDE Plasma was improved.)
Click to expand...
 
dvl@ said:
lgrant Did you try that? I use it on development boxes where I don't want what I'm developing to get installed.
Click to expand...
Not yet, though I intend to look into it. It looks like it will solve the problem of PulseAudio getting installed accidentally. But will the packages that use it still install, and then fall over when they try to use it. Or will it keep them from installing? (I still have to learn more about the packaging system.)
 
lgrant said:
Not yet, though I intend to look into it. It looks like it will solve the problem of PulseAudio getting installed accidentally. But will the packages that use it still install, and then fall over when they try to use it. Or will it keep them from installing? (I still have to learn more about the packaging system.)
Click to expand...
The packages using PulseAudio will still get installed. They might fall over.
 
You must log in or register to reply here.
Back
Top