forked from linuxmint/mint-themes
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Flatpak/Flathub availability #12
Labels
enhancement
New feature or request
Comments
Hello @feathersAndFury,
P.S.: Let me know when you succeed in uploading this to FlatHub. I could put a link to your work from the README.md home page. |
Hello @feathersAndFury |
Thank you! I'm trying to set up a flatpak build environment at the moment,
so I'm just gonna keep messing with it until I get it working. My intent is
to stay exactly even with your repo.
…On Wed, Dec 2, 2020 at 5:57 PM Sébastien Bouchard ***@***.***> wrote:
Hello @feathersAndFury <https://github.com/feathersAndFury>
I see you forked my repo. Great. I just wanted you to know there is a
color update coming very soon. In the next hours. Stay tuned!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQR2BTLE23LMGSZDZAHTXFLSS3A6ZANCNFSM4TECK7TQ>
.
|
Hello @feathersAndFury |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello Sébastien!
One of the aspects of GTK+ theming that's most important is consistency across programs, and I'm concerned that without a Flathub packaging of Mint-Yz, it is difficult to achieve this goal. As Mint is an LTS distro, users are more drawn to containerized apps as releases age. Having them default to Adwaita when Mint-Yz is enabled is jarring and unfortunate. While I have no experience in Flathub development, I am a student and have a good bit of time on my hands. I'd love to work on packaging this for the benefit of the community (and GPLv3 allows me to!), but I wanted to check with you first!
The text was updated successfully, but these errors were encountered: