Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid presence of Binary and Container signature files in more than one location in the codebase #1105

Open
sparkhi opened this issue May 10, 2024 · 0 comments
Open

Avoid presence of Binary and Container signature files in more than one location in the codebase #1105

sparkhi opened this issue May 10, 2024 · 0 comments
Labels
to-be-done-by-tna Task reserved to TNA developers (conflicts with existing work, requires TNA supervision)

Comments

@sparkhi
Copy link
Collaborator

sparkhi commented May 10, 2024

The signature files are in multiple locations, they are used for testing as well as the latest files are bundled in the distributable binary. We definitely need one set to be bundled in the binaries, however, can the other places avoid having a copy?
@sparkhi sparkhi changed the title Avoid the presence of Binary and Container signature files in more than one location in the codebase Avoid presence of Binary and Container signature files in more than one location in the codebase May 10, 2024
@sparkhi sparkhi added the to-be-done-by-tna Task reserved to TNA developers (conflicts with existing work, requires TNA supervision) label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
to-be-done-by-tna Task reserved to TNA developers (conflicts with existing work, requires TNA supervision)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sparkhi