Even having gnome profile set on my systems (that enable gtk USE flag by default), I got surprised when I saw I had no GUI at all for mkvtoolnix package. That was caused by it using "wxwidgets" instead. That doesn't look too reasonable to me when no other gtk GUI alternative is provided and, then, I would move "wxwidgets" to "gtk" USE flag to get mkvtoolnix's gtk GUI installed Thanks Reproducible: Always
No other ebuild in the tree appears to do this, probably due to the global definition for the gtk use flag stating the use of x11-libs/gtk+. Anyway, I don't really see a need for this, but I'm partially biased since I never use the GUI anyway. :)
-1 from me, it's correct the way it is -- USE=wxwidgets is being used as designed
But people having a global "gtk" USE flag set expects to have gtk based GUIs enabled, if it's being used "as designed" (I don't know where are that "designs" also) it's wrongly designed I think, as this packages doesn't have any other gtk gui available
I meant USE=wxwidgets is for controlling wxwidgets toolkit/gui as per description with 'as designed'. I see 4 different ways of solving this: IUSE="+wxwidgets" or in desktop profile, 'media-video/mkvtoolnix wxwidgets' in package.use or 'wxwidgets' in make.defaults if the latter, propose to enable it by default in the ML. Or do nothing and leave it the way it is.
Maybe I should suggest in ML to USE "gtk" USE flag as first option when package doesn't have any other gtk gui than wxGTK based one, and, then, use "wxwidgets" when there is another "gtk" gui to fit there. That way would also fit inside "gtk" USE flag description: gtk - Adds support for x11-libs/gtk+ (The GIMP Toolkit)
why do you assume wxwidgets means gtk ? from http://wxwidgets.org/downloads/ : wxMSW - installer for sources (not binaries) Windows, with manual wxGTK wxMac wxX11 Other ports (Motif, OS/2, MGL, Base) and releases
(In reply to comment #6) > why do you assume wxwidgets means gtk ? Because in this case it means gtk gui
(In reply to comment #7) > (In reply to comment #6) > > why do you assume wxwidgets means gtk ? > > > Because in this case it means gtk gui _today_ if some day we have have other wxwidgets implementations, we'll have to revert it. gtk based desktop profiles should rather enable wxwidgets by default
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > why do you assume wxwidgets means gtk ? > > > > > > Because in this case it means gtk gui > > _today_ > if some day we have have other wxwidgets implementations, we'll have to > revert it. > No, we will need to handle that new situation to allow people to select what implementation to use and, then, try to get gtk based GUIs build with gtk related profiles > gtk based desktop profiles should rather enable wxwidgets by default
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > why do you assume wxwidgets means gtk ? > > > > > > > > > Because in this case it means gtk gui > > > > _today_ > > if some day we have have other wxwidgets implementations, we'll have to > > revert it. > > > > No, we will need to handle that new situation to allow people to select what > implementation to use and, then, try to get gtk based GUIs build with gtk > related profiles I dont understand what you meant and how this relates to this :( (In reply to comment #5) > Maybe I should suggest in ML to USE "gtk" USE flag as first option when > package doesn't have any other gtk gui than wxGTK based one, and, then, use > "wxwidgets" when there is another "gtk" gui to fit there. That way would > also fit inside "gtk" USE flag description: > gtk - Adds support for x11-libs/gtk+ (The GIMP Toolkit) which, to me, makes as much sense as merging gtk and qt useflags under the X useflag because they both need X. Or rather, tell people to use the X useflag if qt or gtk is the only available gui.
(In reply to comment #9) nah, it's mostly about platform/OS and you can't eselect that. aballier seems to be accurate, and I agree the only way to proceed here is to ask USE='wxwidgets' to be enabled by default in the desktop profile. it seems to make sense for the other packages using wxwidgets too, after quick grep through the tree. so unless you are going to propose that in the ML, i'm inclined to close this as WONTFIX
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > (In reply to comment #7) > > > > (In reply to comment #6) > > > > > why do you assume wxwidgets means gtk ? > > > > > > > > > > > > Because in this case it means gtk gui > > > > > > _today_ > > > if some day we have have other wxwidgets implementations, we'll have to > > > revert it. > > > > > > > No, we will need to handle that new situation to allow people to select what > > implementation to use and, then, try to get gtk based GUIs build with gtk > > related profiles > > I dont understand what you meant and how this relates to this :( You suggested that we should revert it if we, for example, include motif port, but I don't think having all that ports inside the same "wxwidgets" flag would be much sense :-/ (In reply to comment #11) > (In reply to comment #9) > > nah, it's mostly about platform/OS and you can't eselect that. > aballier seems to be accurate, and I agree the only way to proceed here is > to ask USE='wxwidgets' to be enabled by default in the desktop profile. it > seems to make sense for the other packages using wxwidgets too, after quick > grep through the tree. > so unless you are going to propose that in the ML, i'm inclined to close > this as WONTFIX Will mail to gentoo-dev as either wait (moving to "gtk" or enabling "wxwidgets" by default) will need discussion
there is just no way 'wxwidgets' is getting renamed to 'gtk', it's like Comment #10 says, same thing as renaming 'qt4' to 'gtk'
Just change it to USE="+wxwidgets" or rename it "gui" or something. I have no opinion about making it default in the profiles. It's probably a good idea. If you do, please make it default for desktop and not just desktop/gnome. We're not renaming it "gtk". They're completely different toolkits. I have no plans to add other implementations until we get preserve-libs in stable or some kind of install-time library reverse-dependency tracking, but someone else might be adventuresome enough one day. I think prefix ha[s|d] a wxMac port going.
OK, as I pointed in ML I was clearly wrong with my interpretation of wxwidgets USE flag meaning, sorry to Samuli and Alexis for his time :-(.
This was fixed as the change was committed to desktop profiles yesterday