Budgie main dev leaves Solus

not everyone has the same taste in themes or icons; for me :frowning: budgie = black plata and gnome)and I put the same thing on solus and opensuse

But it is the default theme/iconset used on GTK and we do already ship GTK Desktops with arc-X icons and arc-gtk-theme installed so user can change to them from settings.

The next release will blacklist Adwaita’s icon theme due to it being broken on Budgie, so you should be able to ship a different icon theme and have it be picked up by Budgie by default. @JoshStrobl can correct me if I’m mistaken.

This will also remove the GNOME feed from showing as menu icon :wink:
But will it need to provide gtk config?
as adwaita is installed anyway as a dependency of a dozen of apps.

Hi @JoshStrobl , great to hear this! I’m really glad that you’re not limiting it to a specific boutique distro. I’m looking forward to carrying on shipping Budgie spins of GeckoLinux; and as for the openSUSE packages I depend on, the key guy is Callum Farmer (on GitHub and openSUSE Build Service), he’s always been great to work with. Feel free to let me know if you have any other thoughts over on the GeckoLinux Github forum. Cheers.

Can you add turkeys in your DE? Like, add an option to change the error sound to a turkey sound or something. It would be funny to have a preset for that

hello,GeckoLinux is very good "except you have to install the translations after installation

Hi there! Yes, I admit that the language support situation isn’t ideal. The problem is that the openSUSE base system is designed to install language packages via the “recommended” (soft dependencies) of packages, which to reduce unwanted bloat I disable by default in GeckoLinux. I don’t think that it should be done that way via recommended packages, but it is what it is. So instead I have to use a regexp script that automatically installs the language support packs. Another common tripping point is a Calamares limitation that requires performing this step on the installed system:

welcome

2 Likes

Hi there, thanks a lot! BTW thanks too for your Calamares configs, just yesterday I poached a few ideas from there that helped me figure out how to use multiple contextualprocess instances and thus solved a blocking issue for the next GeckoLinux release. :+1:

I have promoted your user account to TL1 as new users have a limit on posts. :hugs:

Welcome to @JoshStrobl @serebit and @GeckoLinux :hugs: :enos_flag:

Welcome also @serebit and @GeckoLinux

So. . . theoretically - if budgie-desktop in the Arch repos was configured and setup with a font other than aidwaita. . . and as a base dependency of budgie-desktop . . . . it could be “pre-configured” without being shipped by us as we don’t configure anything . . .

https://archlinux.org/packages/community/x86_64/budgie-desktop/

Does that make sense? Is that correct @joekamprad ?

Yeah I think getting control or contributing to the budgie arch repo would be the go then all arch users would get a nice budgie install not just EOS users

But then that forces a certain configuration, which is probably not the Arch-way. Distros will want to customize.

Going all out with customization is certainly not what Budgie needs - for as you say, its not the Arch -way. I agree.
But if you install Budgie right now from Arch repo, the default config is a total mess, which sure must’ve put away many potential users. The default Budgie should atleast be presentable and usable (like KDE Plasma is) :slight_smile:

Point! I have never installed Budgie except on Solus, so I was unaware. Yes, it should be usable if vanilla.

Budgie on Solus is a very “premium” experience. :wink:

That was more my point, updating the vanilla install to be what the devs want