https://bugs.kde.org/show_bug.cgi?id=506585
--- Comment #6 from Volker Krause <[email protected]> --- So rather than special-casing that in the script, the cleaner solution would probably be to create a separate product for kitinerary then? That should have little impact on anything else as it wont touch the existing product which is referenced in released software and it only relates to an internal library and thus isn't particularly user-facing. Having kitinerary follow standard Gear versioning would also solve this, but given how that is tied into the PIM dependency tree that might have unpredictable side-effects I fear. -- You are receiving this mail because: You are watching all bug changes.
