-
-
Notifications
You must be signed in to change notification settings - Fork 989
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
(chore): Explicit declaration of source(bucket name) of suggested manifests #4409
Conversation
This seems to be a huge change: a simpler alternative would be to just prepend |
Not really, many manifests from Implement it in Scoop Core may breaks 3rd-party buckets and specific scenarios. this is also the reason why I have not changed Adding bucket name for suggested manifests does not affect the existing functionality and we can restore them easily. |
Yes, this is precisely why I'm advocating against this. We follow a convention - a simple one - if the suggestion is from the default bucket of Scoop (i.e. Main), then no need to specify bucket, if it is from elsewhere (even official ones) we need to specify bucket.
That's on them - they did not follow the convention. It has been present since a long time. Not to mention that I'm against commits that modify so many files at once - it pollutes the git history. Also, how is it related to ScoopInstaller/Scoop#5131? I mean how exactly does the |
Scoop does not have bucket sorting settings, and the main bucket does not have the highest weight when manifest selecting. On this premise, as a package manager Scoop must prompt|install exactly the packages that are actually suggested|depended when writing the manifest. IMO |
Hmm, @niheaven any thoughts on this? |
It's strange that I remembered we only recommend omitting Okay, I've submitted a PR in Scoop Core, and please review if it could fix the bug. |
Relates to ScoopInstaller/Scoop#5131