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.

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

[Bug] qmk setup command should not require a yes answer to cloning the qmk_firmware repo to install dependencies #23036

Open
2 tasks
benjistokman opened this issue Feb 8, 2024 · 4 comments

Comments

@benjistokman
Copy link

Describe the Bug

qmk setup should not require a yes answer to cloning the qmk_firmware repo to install dependencies. I only wanted to install the dependencies, not clone the repository.

Keyboard Used

No response

Link to product page (if applicable)

No response

Operating System

No response

qmk doctor Output

No response

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

@tzarc
Copy link
Member

tzarc commented Feb 8, 2024

This is a chicken-and-egg problem, the dependency installation scripts live within QMK Firmware.

I'm not sure what you're asking for is achievable -- if you're not building for QMK you probably don't need the dependencies?

@benjistokman
Copy link
Author

benjistokman commented Feb 8, 2024 via email

@fauxpark
Copy link
Member

fauxpark commented Feb 8, 2024

The install scripts are a little too lengthy for that.

@tzarc
Copy link
Member

tzarc commented Feb 14, 2024

....and for normal distributions, require sudo access. So you'll likely need to inspect the installation scripts, build the dependencies yourself and place them on $PATH inside the user account.

I'm all for keeping things self-contained, but asking users who aren't necessarily familiar with Unix-isms to build their own tooling is probably a bridge too far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants