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

Disable building when there are some errors in the manifest #78

Closed
Tracked by #79
SeaDve opened this issue Feb 22, 2022 · 1 comment · Fixed by #130
Closed
Tracked by #79

Disable building when there are some errors in the manifest #78

SeaDve opened this issue Feb 22, 2022 · 1 comment · Fixed by #130

Comments

@SeaDve
Copy link
Collaborator

SeaDve commented Feb 22, 2022

Related with #1

There could also be message about the missing runtime on the #71's active manifest status bar item.

@bilelmoussaoui
Copy link
Owner

The same would be needed for sdk extensions. So we probably need some way to get that information at first run and re-check later on somehow because the user might install those. The biggest issue with SDK extensions is we will need to resolve the version that should be installed; so rust-stable sdk extension with the GNOME Sdk 41, should map to fdo 21.08 and so to rust-stable//21.08 instead of rust-stable//41 which doesn't exists.

Once we can do all of this and we have that information, we could easily implement something to allow the user installing them like mentioned on #1 on top of that

@SeaDve SeaDve changed the title Disable building when runtime is not available Disable building when there are some errors in the manifest Feb 26, 2022
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 a pull request may close this issue.

2 participants