From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] tunning use flag
Date: Fri, 14 Apr 2006 12:40:05 +0200 [thread overview]
Message-ID: <358eca8f0604140340n3847c95aq98fceff098d4bdeb@mail.gmail.com> (raw)
In-Reply-To: <7573e9640604130905s112896dah9ad7a2a73e283916@mail.gmail.com>
In the fluxbox case it integrates KDE with fluxbox. So, when you run
startkde from a terminal in fluxbox, or you launch KDE applications,
you get System Tray notifications nicely fitting in the fluxbox slit.
On 13/04/06, Richard Fish <bigfish@asmallpond.org> wrote:
> On 4/13/06, Pawel K <pawlaczus@yahoo.com> wrote:
> > How can I find out what I loose by disabling specific
> > flag ?
> > equery uses <pks>
> > shows general info only.
>
> If you are exceptionally lucky, "grep -e "^kde " -e ":kde"
> /usr/portage/profiles/use.*desc" will tell you what it does, or you
> can determine this from the ebuild comments or script.
>
> If you are very lucky, a google search with the appropriate terms will
> tell you. You need to know that "econf ... $(use_enable kde)
> translates to "./configure ... --enable-kde". So a google for
> "fluxbox configure --enable-kde" might help.
>
> If you are a little lucky, there will be a README or INSTALL file in
> the source tarball that will explain exactly what the configure
> options do.
>
> If you have any luck at all, you can interrupt the compile process, cd
> to the package build directory in /var/tmp/portage, and run
> ./configure --help to get documentation about what the option does.
>
> But in the normal case, you have to read the source to really
> understand what impact a use flag has. Or experiment with it on and
> off.
>
> Cheers,
> -Richard
>
> --
> gentoo-user@gentoo.org mailing list
>
>
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-04-14 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 14:34 [gentoo-user] tunning use flag Pawel K
2006-04-12 14:48 ` Gogiel
2006-04-12 21:15 ` Joshua Schmidlkofer
2006-04-12 15:09 ` Richard Fish
2006-04-13 14:44 ` Pawel K
2006-04-13 15:08 ` Neil Bothwick
2006-04-13 16:05 ` Richard Fish
2006-04-14 10:40 ` Mick [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=358eca8f0604140340n3847c95aq98fceff098d4bdeb@mail.gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox