anchore / anchore/binny

Support Windows

Open
#17 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
57
Forks
10
Avg merge
5d 9h
Merged PRs (30d)
7

Description

We'd like to release binny for Windows so that projects using binny to manager their binary dependencies are easier to work on on Windows.

Right now, there are a few obstacles to this:

1. Binny doesn't compile on Windows due to directly using the `syscall.SIGWINCH` constant, which doesn't exist on Windows. To fix that, we should pull all the fancy terminal UI stuff into separate files that aren't built on Windows.
2. Binny has no Windows CI - we should get at least unit tests running on Windows
3. Binny has no Windows release artifacts - this should be a simple goreleaser config change
4. Binny has no Windows-compatible install script. Maybe adding `install.ps1` to the repo, or maybe publishing to chocalatey is the right path here.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Go code that directly uses syscall.SIGWINCH and identify the terminal UI files that need separate Windows build handling. Then inspect the CI and GoReleaser configuration for Windows tests and release artifacts, and evaluate the install.ps1 versus Chocolatey option. Done means Binny compiles, runs unit tests, ships Windows artifacts, and has a Windows installation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ci-cd, cli, operating-systems, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.