Hi Andrew, Thanks, I suspected that might the case. Would that field then only be populated for a package loaded from its tarball form via `alpm_pkg_load`? If that's the case, would it be reasonable to have the DB track this information in general at package install-time? On 7/15/22 17:01, Andrew Gregory wrote:

On 07/15/22 at 03:47pm, Colin Woodbury wrote:

...

Hi guys, I have a brief question about the `makedepends` field of the `alpm_pkg_t` type. Try as I might, I'm unable to get this field to report anything (i.e. a non-empty alpm_list) for installed packages originally from the AUR that definitely had makedepends. This seems to be the case even when those makedepends are still installed.

Under what circumstances should this field be expected to yield results? To be clear, I'm accessing it via the top-level `_pkg_get_makedepends` function. Makedepends are not tracked for installed packages.