Skip to content

"buildable: False" should fail the current configuration #224

Closed
@bos

Description

@bos

(Imported from Trac #231, reported by @dcoutts on 2008-02-05)

Currently resolving configurations does not take account of the buildable field. It should act rather like build-depends: non-existant, though with a different error message.

If possible the error message should relate to the guard condition expression (the conjunction if there are several nested guards).

At the moment it is not considered at all and we don't notice that the package cannot be built until the build step, rather than the configure step.

One problem is that it's not clear if buildable: False is always fatal. People sometimes do that for test executables that are not supposed to be installed. So what should the behaviour be? The lib or only exe failing to configure must be an error.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions