alinaliBQ commented on issue #49404:
URL: https://github.com/apache/arrow/issues/49404#issuecomment-4071248636
1. For signing, we can add a new step to upload the raw materials for
installer. I think existing ODBC MSI upload can be kept for the nightly
package.
2. To start, I can experiment on converting ODBC to static linkage on
Windows.
3. For `07-flightsqlodbc-upload.sh`, this is my understanding based on the
discussion:
How does this flow sound?
i. Download materials from workflow run id -> sign ODBC DLL -> upload to
GitHub release.
ii. `gh workflow run` to trigger workflow that retrieves signed
materials from GitHub release and runs `cpack` to generate MSI, then uploads
unsigned MSI to GitHub release. Wait until the workflow run is finished with
`gh run watch`.
iii. Download ODBC MSI -> sign ODBC MSI -> upload to GitHub release.
If we have new script `07-flightsqlodbc-upload.sh`, then I imagine the
existing ODBC-related code in `04-binary-download.sh` and `05-binary-upload.sh`
will need to be removed as well.
Later I can create issues for 1) upload the raw materials for installer and
2) static Windows ODBC linkage and post here. I can raise the issues for 3)
`07-flightsqlodbc-upload.sh` after we reach consensus
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
