-
-
Notifications
You must be signed in to change notification settings - Fork 17
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.
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
Support executables that aren't in an archive #138
Comments
@binyomen That sounds like a good idea!
But it makes sense to support them from other platforms as well 🙂 |
Huh, weird, that doesn't seem to work for me. With the config: store_directory = '~/bin'
[marksman]
owner = 'artempyanykh'
repo = 'marksman'
asset_name.windows = 'marksman.exe' I get the output:
This is on Windows 11 and tool-sync version 0.2.0. |
@binyomen Huh, that is weird. I'd expect this work. I don't have access to Windows so I would start debugging this issue by adding a test for downloading tool-sync/.github/workflows/ci.yml Lines 69 to 82 in 5d1a6b6
At this point, I'm not even sure where exactly this is coming from so a better investigation is required 🕵🏻 |
Thanks for the tip! I'll have a look at this when I get the chance! |
somehow changing Ok(_tool_path) => {
copy_file(
download_info.archive_path,
self.store_directory,
&tool_asset.exe_name,
)?; and Some types in |
It looks like the issue is that for marksman for example, the path passed to I'm working on a fix now. |
I'm thinking this would be useful for repos like marksman which store the executables as top-level assets rather than in archives.
Thanks! I was about to make this tool myself when I saw someone had just recently started it!
The text was updated successfully, but these errors were encountered: