pkg debendency override
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 23 Nov 2025 13:28:52 UTC
Hi,
I do want to solve upgrading mu, but I also want to learn how pkg
works.
I am on emacs-30.2,3 and mu-1.8.13_4.
I use the emacs window manager exwm as window manager, so I do not
want to uninstall emacs.
# pkg upgrade
The following 7 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
emacs-nox: 30.2,3 [FreeBSD]
Installed packages to be UPGRADED:
mu: 1.8.13_4 -> 1.12.13 [FreeBSD]
Installed packages to be REMOVED:
emacs: 30.2,3
mu4e: 1.8.13_12
pdf-tools: 1.1.0_14
tablist: 1.0.13_11
yaml.el: 1.2.1
Number of packages to be removed: 5
Number of packages to be installed: 1
Number of packages to be upgraded: 1
$ pkg rquery %do mu
databases/xapian-core
devel/readline
devel/libfmt
mail/gmime30
devel/glib20
devel/gettext-runtime
editors/emacs
$ pkg rquery %ro emacs-nox
...
mail/mu
...
My main questions are:
How do I tell pkg that emacs should be ok, no emacs-nox needed? I
tried pkg set -o editors/emacs-nox:editors/emacs
The last commit on mail/mu did not update the DISTVERSION or
PORTREVISION, so how do I tell which version made it into pkg?
If the last commit made it into pkg, where does the runtime
dependency on emacs-nox come from? As I read
https://cgit.freebsd.org/ports/tree/mail/mu/Makefile emacs@nox is
only a manpages build dependency.
Best regards
Markus