-
Notifications
You must be signed in to change notification settings - Fork 777
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
snap: build from source tarball #6831
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment, definitely want @kenvandine's thoughts on this. I like it!
snap/snapcraft.yaml
Outdated
@@ -80,7 +79,7 @@ parts: | |||
- patchelf | |||
- gettext | |||
override-build: | | |||
craftctl set version=$(git describe --abbrev=8) | |||
craftctl set version=$(cat .version) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is . version generated? The nice thing about git describe can be useful to create a meaningful version string that has a relationship to a commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version for dev builds will look like this: 1.1.3-HEAD+88ff566e
, matching ghostty +version
shows and the "about" panel. It's all sourced from the same string. Release builds would show up as-is like 1.2.0
.
87f882c
to
5e06e4b
Compare
Eliminates the need for
blueprint-compiler
, which isn't quite new enough on the snap builder.