[Pkg-electronics-devel] KiCad 7.0 backport to bullseye

[Simon Richter]

Hi,

KiCad 7.0 now requires wxWidgets 3.2, and a wxPython version that has 
been compiled against the same wxWidgets version.

Of course, that is a massive problem for the backport. I have 
successfully built KiCad against backported wxWidgets and wxPython, 
these only require minimal changes, if at all.

The complications are:

  - wxPython from sid requires sip6 to build. This can be almost 
trivially backported (needed a small adjustment because older distutils 
does not automatically add LICENSE files), but I wonder if it makes 
sense to have a backport that's only used as a build dependency.

  - There is no way to depend on a wxPython version that uses a 
particular version of wxWidgets

KiCad should be the only package that actually has a strong version 
constraint because it shares its own objects with wxPython, so we could 
probably make a stronger dependency here for the backport, but it would 
be cleaner to have a "wxpython-linked-against-3.2" virtual package or 
something similar.

Current state is at https://psi5.com/~geier/wx/ -- this is everything 
but KiCad itself.

Does anyone have any strong feelings on how the KiCad 7.0 backport 
should work?

    Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xEBF67A846AABE354.asc
Type: application/pgp-keys
Size: 9675 bytes
Desc: OpenPGP public key
URL: <http://alioth-lists.debian.net/pipermail/pkg-electronics-devel/attachments/20230114/9bad1c60/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-electronics-devel/attachments/20230114/9bad1c60/attachment.sig>