Skip to content

How should downstream Linux distros handle Qt5/Qt6 coexistance? #13

@hosiet

Description

@hosiet

With kcolorpicker v0.3.0, the solution seemed to be straightforward. It introduced libkColorPicker-Qt5 and libkColorPicker-Qt6. When building shared libraries, they can be installed together without conflict since they are of different names.

With kcolorpicker v0.3.1 ( specifically f58d6ad ), the shared libraries built all have the file name libkColorPicker.so.0.x. This means that the Qt5 and Qt6 versions of shared library cannot be installed together. (In the meanwhile, the headers and CMake files can coexist because they are placed under usr/include/kColorPicker-Qt{5,6}/ and usr/lib/*/cmake/kColorPicker-Qt{5,6}/, respectively.

As Debian packager, I would like to know how you would like us to provide the kColorPicker in Debian and its derivatives (e.g., Ubuntu). Do you expect that everything move to Qt6 as Arch Linux, or do you want to make coexistance possible? That will determine how I change the packaging structure at https://tracker.debian.org/pkg/kcolorpicker .

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions