Magic ! (well, actually TryExec in the session file pointing to the helper in the snap! ;)). More on that in a blog post I plan to write early next week.
Hey @didrocks, a quick snap based question: Seems the theme is able to work out of a snap soon, but what about the theming support for example LibreOffice Snap?
Not really (this is currently done by the snap team itself) and I don’t have an idea of their priorities/timelines. But once implemented, I’ll make sure the communitheme snap works with it
As mentioned on the blog post, there are autogenerated snap support for PR.
This enable users to try a branch work in progress before getting it merged to master.
I got a question today from @frederik-f why this wasn’t working for him on https://github.com/ubuntu/gnome-shell-communitheme/pull/104.
Just to be clear: for security reasons, the hidden token (snap store to push the snap and Github to comment on the PR) aren’t accessible for branches not being in the same repository than the destination target. This is a Travis CI feature.
What it means is that if you want to have automated generated snap before they hit master as part of the PR (as in https://github.com/ubuntu/communitheme-snap-helpers/pull/6), you need to have your source branch under the ubuntu repo instead of your own fork.
I’ve fixed the build script so that people using branches on their own fork don’t have CI failing. Their branches are still building a snap to ensure it works, but not uploaded to the store and thus, no comment appearing:
Note that if you intend to get it merged them soon without having snap previews from your branch, don’t bother Just ensure that future branches follow this!
You didn’t answer to my question (I asked you twice in this topic) which is a prerequisite to the changes:
[quote=“didrocks, post:6, topic:4890”]
All fonts? (there are 4 fonts that people can generally change in Tweaks), or only Title fonts or anything else?[/quote]
@madsrh: I would need an answer quickly on this to make the upload in ubuntu now that beta freeze is lifted.
Now that we are close to the release, if no answer by tomorrow, I won’t be able to push the change, I’m afraid :/. The best would be for you to open a launchpad bug describing the changes, that it won’t impact the default session, and what keys are changed.
Thanks!
@madsrh: Sounds correct! (well, not the correct package, but I’ll retarget). Thanks!
Just to confirm: basically, you only want the interface font to be at 10, as I see it (second options in tweaks)? So, window titles, fixed font and documents stays at their previous defaults.
@c-lobrano & @merlijn-sebrechts: Ok, I have promoted current edge version (fixing gtk2 and electron apps) in the stable channel.
I’ll let you handle further regular promotion from edge to stable from now on
Some quick instructions how to do it:
First time:
install snapcraft
ensure you are logged in via snapcraft login
Then, everytime you want to promote the currently tested snap
snap info communitheme to check which snap revision you are running on
publish that revision to stable channel (and candidate/beta if anyone is using it) via: snapcraft release <your-tested-revision> stable,candidate,edge
you can rerun snap info to ensure everything went alright
I think targetting at having one release a week (and maybe even communicating it on a dedicated thread) would be awesome! Most of people are relying on the stable channel from the first stats, so it’s quite important (and it seems this communitheme snap is getting popular, which is awesome even before 18.04 is released!) I’ll let you organize around this!
As usual, do not hesitate to ask if there is any issue
You can use it as you see edge/stable is the simpliest model, but you can decide to do edge/beta (twice a week)/stable (once a week). Just adapt the snapcraft release command to your needs!