-
Notifications
You must be signed in to change notification settings - Fork 2
PAYG UI #165
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
base: main
Are you sure you want to change the base?
PAYG UI #165
Conversation
f6f464d to
34c21dc
Compare
elements/core/gnome-shell.bst
Outdated
| - kind: git_module | ||
| url: github:ptomato/jasmine-gjs.git | ||
| path: subprojects/jasmine-gjs | ||
| ref: 856465dddbd92e82e574891e1ebc79e17d7b708a |
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.
Surprised that the build dependency gnome-build-meta.bst:core-deps/jasmine-gjs.bst does not help here
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.
I build without github:ptomato/jasmine-gjs.git locally successfully.
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.
Mmh… OK I'll check this out. I wonder why it didn't pick the system-wide one up here.
|
Thanks!
EOS will merge the fixup commits into the related commits when every rebase.
EOS staff will force push it the master branch after test. |
|
Just notice this branch has not rebased on the latest main branch. So, the filesystem has not included eos-payg-nonfree, yet. |
Both EOS non-PAYG and PAYG system share the same OSTree branch. Which means they all have PAYG components. So, install eos-payg.bst and eos-payg-nonfree.bst directly. And, build eos-payg.bst and eos-payg-nonfree.bst by following current eos-payg & eos-payg-nonfree's build configuration. Part-of: #165
Both EOS non-PAYG and PAYG system share the same OSTree branch. Which means they all have PAYG components. So, install eos-payg.bst and eos-payg-nonfree.bst directly. And, build eos-payg.bst and eos-payg-nonfree.bst by following current eos-payg & eos-payg-nonfree's build configuration. Part-of: #165
Build eos-payg.bst and eos-payg-nonfree.bst by following current EOS 6 eos-payg & eos-payg-nonfree's build configuration. Part-of: #165
|
The test needs #199, too |
69b48e6 to
b086cc5
Compare
f4fe0a7 to
2d62d2e
Compare
|
I have squashed the fixup commits in @Kekun's gnome-shell branch, then pushed into EOS gnome-shell as branch 12-gnome-shell-48.4. Please update gnome-shell.bst's source, too. After fix, I think it is good to merge, then let it build and test the image. |
2d62d2e to
3213a5b
Compare
|
Thanks! It's now updated. 🙂 |
|
Let me know if anything is needed from me to merge this. 🙂 |
This overrides GNOME Shell from
gnome-build-metaby https://github.com/Kekun/eos-gnome-shell/tree/eos7.0, a fork of https://github.com/endlessm/gnome-shell that rebases its commits from 43.9 to 48.4.Compared to https://github.com/endlessm/gnome-shell, https://github.com/Kekun/eos-gnome-shell/tree/eos7.0:
I did my best to fix all the build time and runtime issues I encountered, though some may have slipped through. Assume this requires thorough testing as Shell evolved quite a bit in the 2½ years gap that separate 43 from 48.
Once we are happy with the change, how should https://github.com/Kekun/eos-gnome-shell/tree/eos7.0 be upstreamed to https://github.com/endlessm/gnome-shell?
This fixes #12.