https://bugs.kde.org/show_bug.cgi?id=365813
Bug ID: 365813
Summary: options doesn't work for module-sets
Product: kdesrc-build
Version: Git
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: mp...@kde.org
Reporter: fa...@kde.org
I would like to keep using branch-group kf5-qt5 (for KF5 itself, for the
workspace, for most apps, etc.) but I would like to switch to
Applications/16.08 for the kde pim stack.
Reproducible: Always
Steps to Reproduce:
The modules that make up "kde pim" are a very large number (hmm what's the
proper English sentence for this?).
They are defined in 3 module-sets in kf5-kdepim-build-include:
akonadi kde-pimlibs kde-pim
Therefore my attempt, to avoid forking kf5-kdepim-build-include, was to write,
in my kdesrc-buildrc:
include extragear/utils/kdesrc-build/kf5-qt5-build-include
options akonadi
branch Applications/16.08
end options
options kde-pimlibs
branch Applications/16.08
end options
options kde-pim
branch Applications/16.08
end options
Actual Results:
This works well for akonadi, because that's the module name, but not for the
others, e.g. kdesrc-build kde-pimlibs shows
Building kcontacts from kde-pimlibs (1/43)
Updating kcontacts (to branch master)
Expected Results:
Could "options" for a module-set be applied to all the modules of the
module-set ?
Alternatively you might prefer a more explicit module-set-options, don't know
what fits best with kdesrc-build's overall design for modules and module-sets.
--
You are receiving this mail because:
You are watching all bug changes.
