Skip to content

What Linux (Debian) builds should plugin developers push to prod? #1308

@keesverruijt

Description

@keesverruijt

Now that OpenCPN is at 5.12, what is the expectation of plugin developers? Should we still target older OpenCPN releases as well, e.g. keep Debian 10 and 11 builds and Flatpak 22.08 for the plugins? Or do we keep the older plugin release in the metadata directory so that older releases can still download the older versions?

The point is of course that there is only one master and one beta repository for all OpenCPN versions. So when I drop the Debian 10 and 11 builds, anyone still on OpenCPN 5.10 or 5.8 for some reason will no longer see the radar plugin when this is removed from the repository.

I think for this cycle I will just keep older plugin versions in the metadata, as then I know these are built against the proper wx code etc. -- If I rebuild I really also need to verify that it runs with older OpenCPN versions properly, which gets out of hand quickly.

Is the catalog loader smart enough to only present the newest plugin if there are multiple versions in the catalog?

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