'pkg -d' shows bogus dependencies

[yurivict]

In the below output gnat12, chromium, and some or all of gcc* lines are bogus.
Additionally vulkan-loader-1.4.350.0 is displayed twice.

$ pkg info -d ollama
ollama-0.30.9:
        vulkan-loader-1.4.350.0
        openblas-0.3.33,2
        FreeBSD-clibs-15.snap20260604161642 (libc++.so.1)
        FreeBSD-clibs-15.snap20260604161642 (libc.so.7)
        FreeBSD-clibs-15.snap20260604161642 (libcxxrt.so.1)
        FreeBSD-clibs-15.snap20260604161642 (libdl.so.1)
        FreeBSD-clibs-15.snap20260604161642 (libgcc_s.so.1)
        gcc14-14.2.0_4 (libgcc_s.so.1)
        gcc16-16.1.0 (libgcc_s.so.1)
        gcc12-12.4.0_3 (libgcc_s.so.1)
        gnat12-12.4.0 (libgcc_s.so.1)
        FreeBSD-clibs-15.snap20260604161642 (libm.so.5)
        openblas-0.3.33,2 (libopenblas.so.0)
        FreeBSD-clibs-15.snap20260604161642 (libthr.so.3)
        vulkan-loader-1.4.350.0 (libvulkan.so.1)
        chromium-149.0.7827.53 (libvulkan.so.1)

Version: 2.7.5
FreeBSD 15.1 STABLE

[arrowd]

What's wrong about them specifically?

[yurivict]

ollama doesn't depend on chromium and gnat.

[arrowd]

The line gnat12-12.4.0 (libgcc_s.so.1) reads as "ollama depends on libgcc_s.so.1, which can be fulfilled by gnat12". The message might need reformulation to be clearer, but there is nothing bogus about it.

(and chromium probably should not provide libvulkan, but that's a different issue)

[yurivict]

'pkg -d' should show declared dependencies (RUN_DEPENDS in the port).

PKG-INFO(8) says:

     -d, --dependencies
             Display the list of packages on which pkg-name depends.

Actual binary dependencies are:

$ ldd /usr/local/bin/ollama
/usr/local/bin/ollama:
        libthr.so.3 => /lib/libthr.so.3 (0x64a1e8d4000)
        libc++.so.1 => /lib/libc++.so.1 (0x64a1f9c1000)
        libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x64a20446000)
        libdl.so.1 => /usr/lib/libdl.so.1 (0x64a2139a000)
        libc.so.7 => /lib/libc.so.7 (0x64a2227c000)
        libsys.so.7 => /lib/libsys.so.7 (0x64a23517000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x64a24130000)
        [vdso] (0x64a1df02000)

libgcc_s.so.1 comes from the base, not from gnat or gcc* packages.
libvulkan.so installed by vulkan-loader is loaded dynamically, but it would be most likely loaded from /usr/local/lib/libvulkan.so.
If libvulkan.so would be loaded from chromium as it is implied by the 'pkg -d' output this would be wrong and would indicate a bug because it isn't known what version is the chromium's libvulkan.so.

[arrowd]

'pkg -d' should show declared dependencies (RUN_DEPENDS in the port).

No, RUN_DEPENDS is a ports thing. A FreeBSD package may be created without any port recipe, and even if it comes from a port, -d does not necessarily equal to RUN_DEPENDS.

libgcc_s.so.1 comes from the base, not from gnat or gcc* packages.

It also comes from gnat and gcc. Moreover, the provides/requires mechanism makes such library dependencies interchangeable, so if you have

foo-1.2.3 (libfoo.so.0)
bar-4.5.6 (libfoo.so.0)

then you can pkg remove foo and it will not cause the dependent package to be removed - the dependency can still be fulfilled by bar.

[yurivict]

You should think from a simple user's perspective.

The user wants to know what does this package depend on. ollama certainly doesn't depend on chromium or gnat, but the user is told that it is with a complicated explanation involving provides/requires.

You expect the user to understand some deep concepts that is really not what he needs and not what he asked.

Contents of RUN_DEPENDS is recorded in the package file. These dependencies should be shown by 'pkg -d' by default.

[arrowd]

You should think from a simple user's perspective.

That's your opinion, not universal truth. For instance, my opinion is that a "simple" user should not even know about the system package management and instead use GUI "store" applications like Plasma Discover, Gnome Software Center or those we're using on Android/iOS.

[yurivict]

Just because chromium, gnat and gcc* happen to provide some files with same names that ollama also uses doesn't qualify them to be listed as dependencies by default. These files are most certainly not used by ollama during its run-time and they also shouldn't be used by ollama. Therefore they should not be listed as dependencies.

The explanation that you provided involves some mental gymnastics which should not be relevant to simple users.

That's your opinion, not universal truth.

Sure. But you should assume that most users are simple users who want simple answers in most cases, this is just a fact of life. And you offer an elaborate explanation of a wrong answer to a very simple question which is just not right in this situation.

[arrowd]

These files are most certainly not used by ollama during its run-time

They do. If you remove the base libgcc_s.so.1, it will pick up the gcc or gnats one. Whether that work is an orthogonal question. Some libraries should not be registered as provided indeed, like libvulkan of chromium, but the general idea holds.

But you should assume that most users are simple users who want simple answers in most cases, this is just a fact of life. And you offer an elaborate explanation of a wrong answer to a very simple question which is just not right in this situation.

You didn't hear me. I'm saying that "simple" users shouldn't even use pkg directly. So they shouldn't know anything not only about libraries, but even about packages and theirs dependencies.

[bapt]

@arrowd is right, I am happy to clarify the mssage if needed

[yurivict]

I disagree with the default output of 'pkg info -d ollama'.
It shows gnat12 and gcc* because when the base libgcc_s.so.1 would be removed these other libs would be used. But base files are not removed in the vast majority of systems.

They should never be removed unless you experiment with this and remove them manually or when some failure has happened.

'pkg info -d {pkg}' should show what the package actually depends on.

There should be an additional flag (for extended info) which should show the info that is currently shown by 'pkg -d'.

For example, we can add a new argument:

-X, --extended-info
        Makes other commands to produce extended info, for example 'pkg info -d'

Then the command 'pkg info -d -X ollama' would print:
chromium-149.0.7827.53 (libvulkan.so.1: additional choice to /lib/libgcc_s.so.1)
Same for other items.

But printing 'chromium' as a default dependency of ollama is simply incorrect.