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

Support folder buckets which are not a git repo #4019

Closed
NotWearingPants opened this issue Jun 10, 2020 · 4 comments
Closed

Support folder buckets which are not a git repo #4019

NotWearingPants opened this issue Jun 10, 2020 · 4 comments

Comments

@NotWearingPants
Copy link

Currently, scoop buckets are a git repo with a bucket folder.
Git is used for auto-updating the package index.

Scoop also supports installing manifests directly - scoop install .\path\to\local\app.json, or scoop install http://example.com/path/to/remote/app.json

Scoop should support something like scoop bucket add local .\path\to\local or scoop bucket add example http://example.com/path/to/remote, which should register the local/remote bucket, and when using scoop install app it should attempt to fetch the manifest from that local directory or url.

@Ash258
Copy link
Contributor

Ash258 commented Jun 10, 2020

Just add the folder to the "$env:SCOOP\buckets"

image

You will see update failure on buckets updates, but nothing critical.

Or just link the folder if desired.

@NotWearingPants
Copy link
Author

Thanks for replying :)

That's my current setup, I opened this issue because I get errors on bucket updates.
Getting errors is very annoying, since I look at the update output to see what's new.

I'm hoping for a less hackish solution, that will also symlink the folder itself.

This solution also doesn't work for remote buckets (with a URL) which are not git repos, although I admit this is not my current use case.

@rashil2000
Copy link
Member

Closed in #4670

@the-nurk
Copy link

the-nurk commented Nov 29, 2023

for those who ended up here, the solution is not here, it's over here:

#5314

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

No branches or pull requests

4 participants