You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Another possibility is to deprecate buildable for this use case and add fail instead which would provide an error message to indicate why a particular configuration is not possible.
The semantics would be slightly different to buildable: False. It would make configuring the whole package fail, not just disable building that executable or library.
Another possibility is to deprecate buildable for this use case and add fail instead which would provide an error message to indicate why a particular configuration is not possible.
I guess fail would have a similiar effect to build-depends: base<0?
(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.
The text was updated successfully, but these errors were encountered: