Add openssl debian package

[padelsbach]

When generating a Debian package for WolfProvider, also include a separate package for openssl (Alternate approach)

[LinuxJedi]

I don't think we need to have the entire wolfSSL source and binaries in this git repo. It would be better to have GitHub Actions to build and cache them. Once wolfSSL/wolfssl#9161 is merged, this should become quite easy.

[padelsbach]

I don't think we need to have the entire wolfSSL source and binaries in this git repo. It would be better to have GitHub Actions to build and cache them. Once wolfSSL/wolfssl#9161 is merged, this should become quite easy.

Sure. The tarball here is just a stop-gap. However, from what I can tell, the packaging.yml in wolfSSL does not seem to save artifacts. Should we add that @LinuxJedi ?

[LinuxJedi]

Sure. The tarball here is just a stop-gap. However, from what I can tell, the packaging.yml in wolfSSL does not seem to save artifacts. Should we add that @LinuxJedi ?

It shouldn't be required. You can pin whatever version of wolfSSL you want without it and just copy the Debian directory over + patch the configure.ac (for older than master once merged).

Unless there is a use case I'm missing?

[padelsbach]

Sure. The tarball here is just a stop-gap. However, from what I can tell, the packaging.yml in wolfSSL does not seem to save artifacts. Should we add that @LinuxJedi ?

It shouldn't be required. You can pin whatever version of wolfSSL you want without it and just copy the Debian directory over + patch the configure.ac (for older than master once merged).

Unless there is a use case I'm missing?

After some offline discussion, the basic flow is:

1. checkout the chosen tag/version of wolfssl
2. copy the debian directory from wolfssl master (post merge of PR 9161)
3. patch wolfssl/configure.ac with the changes from PR 9161
4. build the wolfssl debian package as part of the WP github action (with make deb)