Sweet-v40 as default Garuda theme, instead of Sweet?

I just adore Garuda, it's Arch-based distro I always wanted. But I have this one small issue.

GNOME is my go-to DE when using Linux, I like how Garuda makes it look, but the default "Sweet" theme is not optimized for GNOME 40, which makes icon stick out from dock, overlap, generally it looks pretty bad and sloppy.

But there's a way. "Sweet" creator made GNOME 40 optimized versions of "Sweet" theme. Is there a possibility, that you, devs, change default theme from Sweet to Sweet-v40? It would make Garuda GNOME 40 as pretty as it was on 3.xx GNOME.

Cheers!

1 Like

:eyes: Link?

2 Likes
2 Likes

We use the package sweet-gtk-theme-dark AUR (en) - sweet-gtk-theme-dark

I guess @jonathon or @dr460nf1r3 needs to update it

2 Likes

The upstream project hasn't tagged a new release, which is why the AUR package hasn't been updated.

I'll ask for a new release tag. If nothing happens then I'll look at updating to a commit and inventing a release number. :sweat:

5 Likes

Maybe do it first then wait for upstream to release the tag :sweat_smile:

1 Like

PKGBUILD updated.

5 Likes

Does not build

1 Like

Yup, it's not correct. It needs building with gulp or something. :pensive:

3 Likes

OK, try now? :sweat:

2 Likes

We need to revert this as every existing user will get a not working GTK theme :sweat_smile: creating a separate package would most likely be the better idea :eyes:

1 Like

@dr460nf1r3 do this ship the new theme with old theme name in the settings package for now

and when we release new iso make changes to configs

1 Like

I said the same thing before as well but sgs closed it :frowning_face:

I had it in the to-do list but wasnt able to to much pc work this week. Its done now. sweet-gtk-theme-dark reverted to previous state and created a different package with -v40 suffix which garuda-gnome-settings depends on.

2 Likes

Why's that?

What's the difference? Why do we need to retain the 3.38 version if GNOME is now version 40?

Edit:

OK, so it looks like the initial update caused it to switch to the light theme, but that should have been resolved by the second update, which you then reverted.

2 Likes

The folder name was different so every existing user would have a not working theme after the update. But I just realized I did the same thing in the -v40 variant which solves the issue :thinking:
https://aur.archlinux.org/cgit/aur.git/commit/?h=sweet-gtk-theme-dark-v40&id=5481bffacc85f2c463b549bfcd91c0a9098320a0

2 Likes

This:

  cp -r "${srcdir}/${_pkgname}" "${pkgdir}/usr/share/themes/"
  mv "${pkgdir}/usr/share/themes/Sweet-Dark-v40" "${pkgdir}/usr/share/themes/Sweet-Dark"

could probably be just

  cp -r "${srcdir}/${_pkgname}" "${pkgdir}/usr/share/themes/Sweet-Dark"

So, next question - do we want to make that change in the sweet-theme-* packages?

2 Likes

Alright, done now.

3 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.