Skip to content

Declarative configuration #35

@nponeccop

Description

@nponeccop

I propose to have configuration files to substantially reduce the need for patches, as patches are brittle. As can be seen from recent GHC update, version updates require recommitting of patches as they contain version numbers.

Patches are a good idea because they are universal and allow any type of modification. However, it turns out that most often the only changes needed are changes to the list of dependencies detected by cblrepo. So I propose someting like patches/<pkgname>.override with

depends=+foo -bar +baz

So this information is applied internally by cblrepo to its detected list of dependencies before generation of PKGBUILD and it doesn't contain version numbers so there is no need to maintain it on every update. Then patching proceeds as usual.

The .override files are technically not patches, but putting them in patches/ lets a user to uniformly inspect/remove all overrides by ls patches/<pkgname>.*, rm, vim -p etc. And the config can be extended to support overrides other from depends if we ever decide so.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions