View previous topic :: View next topic |
Author |
Message |
Eniax n00b
Joined: 06 Feb 2018 Posts: 23
|
Posted: Wed Feb 28, 2018 8:01 pm Post subject: Appropriate USE flags for LXDE |
|
|
Apologies if this has been addressed, but I didn't find anything specific to what I'm looking to understand.
I have a laptop with the default desktop profile selected and LXDE installed. That and firefox are the only applications that have been placed on the machine (from a gui perspective). I assume the default desktop profile uses several USE flags for things that I wouldn't need and I'm hoping that someone can help me to understand, or point me in the right direction to find what would work best for me.
Mainly I'm curious if I need both gtk and qt support. I know these are application frameworks but I'm not sure that both are strictly necessary. For example if something was built in qt, will it work if i just emerge everything with explicitly GTK?
Thanks for the help. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Fri Mar 02, 2018 1:26 pm Post subject: |
|
|
If you want a nice GUI, you should enable Qt/GTK for packages that have those use flags. They are perfectly fine coexisting. My systems often have both. Some packages require only-one-of qt4 or qt5, in which case you use package.use to disable one or the other. In the case of both being allowed, that's for compatibility with user requirements/preferences, so just enable one. It's a safe bet to choose higher over lower versions if the flag exists.
For global use flags in general, I recommend you emerge ufed. It's a nice little curses utility that lets you modify your global use flags while seeing descriptions for the flags.
Don't worry too much about the use flags you do and don't need as long as package requirements are met and things work. This is what profiles are for. However, if you want to learn more by doing and observing, you can change your global use flags and/or set flags in package.use and update world to see what happens. Just keep track of what you're doing so you can undo it.
Any global use flag changes need to be followed by running
which is "update, Deep, New-use." _________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
Goverp Advocate
Joined: 07 Mar 2007 Posts: 2008
|
Posted: Sat Mar 03, 2018 12:27 pm Post subject: |
|
|
audiodef wrote: | If you want a nice GUI, you should enable Qt/GTK for packages that have those use flags. They are perfectly fine coexisting. My systems often have both. Some packages require only-one-of qt4 or qt5, in which case you use package.use to disable one or the other. In the case of both being allowed, that's for compatibility with user requirements/preferences, so just enable one. It's a safe bet to choose higher over lower versions if the flag exists.
...
|
audiodef, would the Qt packages work better in LXQt, which IIUC is the active version of LXDE? Though it's hard to tell from the two web sites which is more active, I thought the developer said LXQt was the way to go. _________________ Greybeard |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Sat Mar 03, 2018 1:22 pm Post subject: |
|
|
I looked this up not super-long ago, and I think LXQT is a fork that is more active and current. I put it on my girlfriend's old laptop and I like it.
As far as whether Qt would "work better," that kind of doesn't apply. LXQT is simply a Qt-based desktop. Qt and GTK are different technologies and either would work no better or worse in any specific desktop. There are packages that only use one or the other, so a little mixing is inevitable unless you totally shun packages with the one you don't want for some reason - and there's no real reason to do that. _________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Mar 03, 2018 2:01 pm Post subject: |
|
|
LXQT is a rewrite of lxde which is gtk2 based, which is using qt5.
The developers were looking at upgrading lxde from gtk2 to gtk3 and after some analysis and given the fragile nature of gtk3 (from rev to rev at the time)
they decided to base it on qt5 instead. So they merged with razor (sp?) desktop which was already a qt product, IIRC.
But I haven't looked at it since the early days. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Sun Mar 04, 2018 6:57 am Post subject: |
|
|
Did someone succeed in having lxqt-panel without *kit crap and dbus? |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
Chiitoo Administrator
Joined: 28 Feb 2010 Posts: 2575 Location: Here and Away Again
|
Posted: Mon Mar 05, 2018 11:30 am Post subject: ><)))°€ |
|
|
charles17 wrote: | Did someone succeed in having lxqt-panel without *kit crap and dbus? |
While removing 'dbus' would take a bit more effort, there's a 'policykit' USE-flag that should help in getting rid of the other(s).
Code: | eix -Ic *kit && eix -Ic lxqt-panel
[I] app-crypt/p11-kit (0.23.9{tbz2}@16/12/17): Provides a standard configuration setup for installing PKCS#11
[I] app-portage/gentoolkit (0.4.2{tbz2}@30/01/18): Collection of administration scripts for Gentoo
[I] media-sound/jack-audio-connection-kit (0.125.0{tbz2}@02/02/18): A low-latency audio server
Found 3 matches
[I] lxqt-base/lxqt-panel (9999{tbz2}[2]@27/02/18): LXQt desktop panel and plugins |
audiodef wrote: | Why would you not want policykit and dbus? They're pretty basic system components. |
If I don't need a feature a package provides, I may delve quite deep into getting rid of them, mostly just because I can. :] _________________ Kindest of regardses. |
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Mon Mar 05, 2018 5:37 pm Post subject: Re: ><)))°€ |
|
|
Chiitoo wrote: | charles17 wrote: | Did someone succeed in having lxqt-panel without *kit crap and dbus? |
While removing 'dbus' would take a bit more effort, there's a 'policykit' USE-flag that should help in getting rid of the other(s). |
I see. -mount would reduce much of the annoyances: Quote: | USE=-mount emerge -pvt lxqt-panel |
Then there is lxqt-base/liblxqt wanting qtdbus. Would it work also without? |
|
Back to top |
|
|
Chiitoo Administrator
Joined: 28 Feb 2010 Posts: 2575 Location: Here and Away Again
|
Posted: Mon Mar 05, 2018 6:26 pm Post subject: Re: ><)))°€ |
|
|
charles17 wrote: | I see. -mount would reduce much of the annoyances |
Indeed. I was thinking of mentioning that, too, but the thought escaped from me while posting...
Unfortunately that seems like something that would require going into the sources, and at the very least slapping in some '#ifdef DBUS' entries or so. Seems like an interesting project that I might look into, if I had (or when I have) some more time for things and stuff. :] _________________ Kindest of regardses. |
|
Back to top |
|
|
|