Skip to content

Structured warnings and assertions #5

Description

@ConnorBaker

Important

This should be verified and reference specific code.

meta.broken and meta.platforms (or meta.badPlatforms) produce errors rarely provide actionable information for use in troubleshooting. As an example, a package may be marked as broken if a dependency isn't correctly configured or is an unexpected version; recommending users allow all broken packages is typically an unacceptable action toward resolving that problem.

Nixpkgs should provide support for structured warnings and assertions which describe why a package is marked as unavailable.

See also:

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions