[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]


Dear list,

Trying to plan the future for the OpenCPN package. Upstream is currently shipping a beta, and eventually it will be released and packaged.

In next cycle upstream might update the wxWidgets dependency from 3.0 to 3.1.5. This is problematic, since wxWidgets offers no ABI stability for odd-numbered releases like 3.1 and there is thus no Debian packages available.

Now, normally this should not be a problem since the upstream 3.2 release is due Real Soon, and OpenCPN has rather long cycles release cycles, roughly yearly. However, upstream wxWidgets seems stalled, and we are probably facing a real risk that 3.2 is still not available for next OpenCPN release in about a year.

So, the question: would it be acceptable to bundle the wxWidgets 3.1.5 sources in next OpenCPN release in such a situation?



Reply to: