Make Calligra unstable (master) depend on stable kreport and kproperty components as these are external ones.
Stable and development APIs differ for these deps.
Details
Diff Detail
- Repository
- R499 Metadata for build scripts
- Branch
- master
- Lint
No Linters Available - Unit
No Unit Test Coverage
That syntax has no effect - branch specifiers are not supported on the RHS of the equation (and don't have much of an impact on the LHS either).
With the current CI architecture your requirements here aren't supported.
The upcoming move to tracks should allow this.
Thanks @bcooksley.
@danders @rempt, so my conclusion is to set kreport/kproperty 3.1 alpha as a minimum for calligra 3.1. But I see calligra master is 3.0.1. So I am not sure how it all fits together -- don't we need a place for unstable development of calligra?
For the record: KReport/KProperty 3.0 is not API-stable, it was not is KDEreview and such, 3.1 will be, I hope.
I have deactivated reports atm. I will wait for kreport/kproperty to be stable so no need to make any special adjustments.
Thanks for the info @danders. If you have time you can try to reactivate for the current master, or you can wait - we're close to ship Beta 3.1.
3.1.0 has been released and has guaranteed API stability. I see plan/CMakeLists.txt depends on it so I would drop this patch.