Open rgleason opened 1 year ago
What does the jammy build do that the ubuntu & debian builds not do. Is there a real issue with the installables?
As we have said before, jammy is a special case. It identifies as being derived from Debian 12, but is does not offer wx32 in standard repos. Official debian/12 does offer wx32. So we decided to provide a private build of wx32 for jammy, in order to stay consistent with upstream debian state. Management of the wx32 situation is the difference.
Tried attacking the jammy problem a slightly different way. Have added the ability to have job specific extra installs. Have done this for wx3.2 for jammy using the standard build. Just need a test of it.
So does it need the 'special' WX32 in the tuple? If so, are there now two builds for jammy, one with and one without wx32?
Here is the tuple for, e.g. o-charts for jammy:
<target>debian-wx32-x86_64</target>
<target-version>11</target-version>
<target-arch>x86_64</target-arch>
There is no need for a Jammy build without wx32. Official OpenCPN 5.8.x+ uses wx32 for Jammy. Alternatively, any privately made OCPN 5.8 for Jammy without wx32 will be able to load "debian-11" plugins automatically.
I have just created OD 1.6.26.7 in opencpn/alpha so that the jammy version can be tested (there is a pull request in plugins for it).
Bdbcat - scaling of icons Bdbcat - double scaling of text size Rick & Bdbcat -TP 1.0.238 revisions and clarification of circleci/config.yml file to match TP Template Table
PS: This one 1.8.26 + TP1.0.138 should have been labeled "1.8.26+ TP1.0.238" sorry.
Also see PR for Testplugin 1.0.238 + revise config yml rm ubuntu add jammy #314 needs to be accepted. Thanks.