Make gnome-themes-standard setup as gtk2 and 3 theme automatically

[c.herbig@…]

Currently the port tells users to enter a few commands to make it the default gtk3 theme. It does not provide instructions for enabling it on gtk2. I think that it would be reasonable for this port to run those commands automatically after it is installed; that is to say I don't think it's audacious for it to assume that it is the primary theme being installed and that it can take the liberty of setting itself up.

Or perhaps it could be done as a variant, say 'auto_setup'?

[cooljeanius (Eric Gallager)]

Cc Me!

[larryv (Lawrence Velázquez)]

I do not think it is a good idea for ports to automatically alter users’ configuration files in this fashion, or provide an option for doing so.

[c.herbig@…]

Replying to larryv@…:

I do not think it is a good idea for ports to automatically alter users’ configuration files in this fashion, or provide an option for doing so.

I suppose it could become a sticky situation if there is already something in ~/.config/gtk-3.0/settings.ini but it could perhaps be dealt with using a similar method to how macports appends it's stuff to an existing .profile

Ultimately, I would like to create some sort of port that installs and configures a basic, minimal Gtk environment for not-so-technical users, such as fellow students, faculty and associates. They often balk at the command line, finding it intimidating enough even for copy and pasting commands. Essentially, if there was a way to just tell them, for example, you can have a free program for drawing chemical diagrams and reactions by just installing macports, then some-port, it would be much better than trying to convince them to do: Install MacPorts, then Xcode, then install the command line utils from Xcode, then install an X11 server, configure it, then some-package, and then to not make it look ugly, install some-theme, then configure it by hand.

I suppose the reason I thought using a variant to accomplish this would be good is that it requires that extra, deliberate piece that ensures that's what the user wanted it to do. I agree that it could be a bit rude for it to just assume that it can modify a users files just by default.

[c.herbig@…]

Some additional thoughts:

The gtk-chtheme port (which only works for gtk2 right now) takes complete control of the .gtkrc-2.0 file and instructs the user not to edit it, because the next time it is run, it will just rewrite it. As such, having gnome-themes-standard write to either file is not without precedent.

Additionally, giving a theme starting point that sets itself up will probably be quite suitable for most users, whereas people who want to play with other themes can simply configure them themselves, which is what everyone currently has to do right now anyway.

[c.herbig@…]

Perhaps a better solution would be for the script to check to see if ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini already exist. If they do, then leave them alone and let the user figure it out since they seem to have an idea of this already, if they don't exist, then create the files.

[photor@…]

How to enter a few commands to pick a default gtk3 theme? ~/.config/gtk-3.0/settings.ini seems not working.

[chrstphrchvz (Christopher Chavez)]

gnome-themes-standard is obsolete and past its removal date. Does this ticket apply to its replacement, adwaita-icon-theme?

[dbevans (David B. Evans)]

Obsolete gnome-themes-standard removed in ​https://github.com/macports/macports-ports/commit/38c50681aca5e69bde73d3671951a1637e2d6342

[dbevans (David B. Evans)]

gtk2 has it's own default theme, Raleigh. It's built in and requires no additional configuration. Similarly, gtk3 requires adwaita-icon-theme which it uses without further configuration. Many app developers expect these themes to be used and tune their interfaces for them. I don't think it's unreasonable for folks who want to experiment with other themes to have to learn how to configure them. And, as can be seen from the conversation here, any attempt to read their minds and provide automatic configuration is bound to provide unwanted/unexpected results at least 50% of the time.

Closing as won't fix.