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

(chore): Explicit declaration of source(bucket name) of suggested manifests #4409

Closed
wants to merge 2 commits into from

Conversation

HUMORCE
Copy link
Member

@HUMORCE HUMORCE commented Feb 1, 2023

Relates to ScoopInstaller/Scoop#5131

@rashil2000
Copy link
Member

This seems to be a huge change: a simpler alternative would be to just prepend main/ (if nothing else is there) in Scoop core itself.

@HUMORCE
Copy link
Member Author

HUMORCE commented Feb 2, 2023

This seems to be a huge change: a simpler alternative would be to just prepend main/ (if nothing else is there) in Scoop core itself.

Not really, many manifests from extras/versions also do not clearly identify.

Implement it in Scoop Core may breaks 3rd-party buckets and specific scenarios. this is also the reason why I have not changed depends.

Adding bucket name for suggested manifests does not affect the existing functionality and we can restore them easily.

@rashil2000
Copy link
Member

Not really, many manifests from extras/versions also do not clearly identify.

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.

Implement it in Scoop Core may breaks 3rd-party buckets and specific scenarios.

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 suggest field let users customize bucket sorting order?

@HUMORCE
Copy link
Member Author

HUMORCE commented Feb 2, 2023

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.
Also, how is it related to ScoopInstaller/Scoop#5131? I mean how exactly does the suggest field let users customize bucket sorting order?

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

@HUMORCE HUMORCE changed the title (chore): Clearly identify bucket of suggested manifest (chore): Explicit declaration of source(bucket name) of suggested manifests Feb 2, 2023
@rashil2000
Copy link
Member

Hmm, @niheaven any thoughts on this?

@niheaven
Copy link
Member

It's strange that I remembered we only recommend omitting main in depends and suggest, so there're many manifests omitted extras and version as @HUMORCE said?

Okay, I've submitted a PR in Scoop Core, and please review if it could fix the bug.

@HUMORCE HUMORCE marked this pull request as draft March 10, 2023 09:24
@HUMORCE
Copy link
Member Author

HUMORCE commented Apr 23, 2023

@HUMORCE HUMORCE closed this Apr 23, 2023
@chawyehsu chawyehsu deleted the source_of_manifests branch May 14, 2024 03:00
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

Successfully merging this pull request may close these issues.

3 participants