Skip to content

Declaring non-Python dependencies #743

Open
@jayvdb

Description

@jayvdb

It would be nice if there was a consistent format for declaring non-Python dependencies.

In many cases they are missing. e.g.
https://bumblebee-status.readthedocs.io/en/main/modules.html#deadbeef mentioned subprocess, which implies it was invoking an executable, but none is mentioned.

As these tend to be OS specific names, I suggest using Repology names in the module metadata. e.g. deadbeef = https://repology.org/project/deadbeef/versions . These identifiers may then be auto-linked in the generated documentation. Repology provides the mapping to distro packages, so users can see the appropriate package name for their distro, and we can also build scripts to work out which distros dont have some binary dependencies. We could also generate a command for each distro which would install all available binary dependencies for that distro.

I have a mostly complete list of executable dependencies per module at https://build.opensuse.org/package/show/X11:windowmanagers/bumblebee-status , but for common executable dependencies they are Requires: or Recommends: at the top level, not per module. e.g. https://repology.org/project/psmisc/versions and https://repology.org/project/wireless-tools/versions are needed by a few modules.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions