microsoft / microsoft/go-sqlcmd
Add user (as well as machine) .msis for all flavors
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
winget supports user and machine installers, we might as well implement the full complement. But for usability we should only do this if we can ensure "machine" is the default, or at least the default when we can detect ODBC sqlcmd is already in the path.
We probably shouldn't do this if we machine isn't the winget default AND we can't tell winget to do machine if we can detect ODBC sqlcmd is already in the path.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the winget packaging for the existing machine .msis across all flavors and how the CLI detects ODBC sqlcmd in PATH. Define the supported user and machine installer variants and verify that installation selects machine scope by default, or when the existing executable is detected. Done means all flavors have the intended .msi options without an unsafe default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100