progska

[jkocz]

progska consistently causes issues for new installs due to the c code compile requirements.

Options are:

1. Remove progska from casperfpga and/or make it a separate package/submodule
2. Remove skarab support entirely from future releases e.g. py310 going forward
3. Update install instructions to ensure progska requirements are met and leave it as is.

I'm more inclined to go with (1) as I don't really like having the c code compile requirements for the python library, but also don't want to remove support for skarab too early - or if a similar type scheme is expected to be needed in the future for other boards.

Comments/alternative solutions appreciated.

[AdamI75]

@jkocz I think it makes sense to go with 1) above to ease the installation process. SKARAB has never really worked with Python 3.6 onwards due to programming issues. I am not sure if this has changed. It is still baselined at Python 2.7. I don't want to remove support for SKARAB as it is way too early for that and many members e.g. INAF are still using this platform. Therefore, removing it from casperfpga and making it a separate package/submodule makes sense to me. The user shouldn't need to install progska if they are not using it, either.