tint2-0.9 and up contain the tint2conf application, formerly known as tintwizard (http://code.google.com/p/tintwizard/). This lets you graphically generate configs for tint2. It's controlled by a configure switch in configure.ac: --enable-tint2conf tint2conf requires pygtk to be installed on the system, so the ebuild needs to be updated with the appropriate USE flag and RDEPENDS.
I'll write an ebuild for tintwizard instead of adding tint2conf useflag. The reason is that the tint2conf switch will enable tint2conf as well.. which is highly experimental and doesn't work properly at all.
(In reply to comment #1) > I'll write an ebuild for tintwizard instead of adding tint2conf useflag. > The reason is that the tint2conf switch will enable tint2conf as well.. which > is highly experimental and doesn't work properly at all. tintwizard may be broken, too. Here's what I get after enabling the built-in version shipped with tint-0.9: $ tintwizard.py Traceback (most recent call last): File "/usr/bin/tintwizard.py", line 2386, in <module> tw = TintWizardGUI() File "/usr/bin/tintwizard.py", line 218, in __init__ self.readConf() File "/usr/bin/tintwizard.py", line 2150, in readConf self.writeConf() File "/usr/bin/tintwizard.py", line 2320, in writeConf f = open(pathName+"/tintwizard.conf", "w") IOError: [Errno 13] Permission denied: '/usr/bin/tintwizard.conf' . . . so it installs to /usr/bin/, as it should, but then I think it's trying to write/create a config file in the same directory, instead of using ~/.tintwizard.conf or ~/.config/whatever.conf. Seems just as broken as tint2conf. Speaking of tint2conf, yeah, it doesn't work for me, either. A useless gtk+ window that doesn't do anything pops up, and there is more broken output on the CLI.
http://code.google.com/p/tintwizard/issues/detail?id=37 Maybe I get to it first otherwise we have to wait some days :P
Tested on x86: No issues.
(In reply to comment #4) > Tested on x86: No issues. Argh. Sorry for that, wrong bug :(
x11-misc/tintwizard has been added to the tree :) So I'll close this bug for now as FIXED and we might reopen it if tint2conf is usable. Thanks
