public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gnome intrusion?
Date: Wed, 16 Nov 2016 21:51:29 +0100	[thread overview]
Message-ID: <20161116215129.0cdc0f02@jupiter.sol.kaishome.de> (raw)
In-Reply-To: CAKpSnp+HYKBU4gUx1Ga-G=8+7ghAZghJ_=TGh_8jYQaTqJstdQ@mail.gmail.com

Am Wed, 16 Nov 2016 11:25:02 +0000
schrieb Jorge Almeida <jjalmeida@gmail.com>:

> On Wed, Nov 16, 2016 at 9:08 AM, Neil Bothwick <neil@digimed.co.uk>
> wrote:
> > On Wed, 16 Nov 2016 07:23:02 +0000, Jorge Almeida wrote:
> >  
> >>  
> > What you're asking is a bit like asking for a complete list of the
> > abilities the python USE flag adds, when all you can really say is
> > it allows the software to run Python scripts, not what those
> > scripts may do.
> >
> >  
> I'm not really asking for exhaustive documentation about  USE flags,
> just saying that even some fragmented documentation would be useful. I
> don't expect a particular contributor to know  everything about a
> particular USE flag. (And, of course, no one is under any obligation
> to do it.)
> 
> All this would be easier if upstream package developers  would explain
> what the different config options really entail. Most of the times,
> "./configure --help" is not that helpful.

One could start a wiki entry for each use flag on the Gentoo wiki.

Also, you can use "euse -i USEFLAGNAME" which is sometimes helpful,
sometimes not - depending on how generic the description is.

-- 
Regards,
Kai

Replies to list-only preferred.



  reply	other threads:[~2016-11-16 20:51 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  9:32 [gentoo-user] gnome intrusion? Jorge Almeida
2016-11-14 17:37 ` [gentoo-user] " Ian Zimmerman
2016-11-14 19:03   ` Jorge Almeida
2016-11-14 20:37 ` Kai Krakow
2016-11-14 21:49   ` Jorge Almeida
2016-11-14 23:51     ` Kai Krakow
2016-11-16 12:47     ` [gentoo-user] sans-dbus was: " Miroslav Rovis
2016-11-16 18:42       ` Jorge Almeida
2016-11-17  1:48         ` Rich Freeman
2016-11-17  7:56           ` [gentoo-user] " Ian Zimmerman
2016-11-17  9:08             ` Rich Freeman
2016-11-19  9:21               ` Kai Krakow
2016-11-19 19:06                 ` Ian Zimmerman
2016-11-19 19:16                   ` Rich Freeman
2016-11-19 20:47                     ` Ian Zimmerman
2016-11-19 21:07                       ` Alan McKinnon
2016-11-19 21:23                         ` Ian Zimmerman
2016-11-19 22:34                           ` Canek Peláez Valdés
2016-11-19 22:36                           ` Alan McKinnon
2016-11-20  0:36                           ` Walter Dnes
2016-11-19 21:59       ` [gentoo-user] " Tom H
2016-11-19 22:15         ` Rich Freeman
2016-11-20 18:40           ` [gentoo-user] " Kai Krakow
2016-11-14 23:38 ` [gentoo-user] " Andrew Tselischev
2016-11-14 23:52   ` Jorge Almeida
2016-11-15 17:39     ` [gentoo-user] " Ian Zimmerman
2016-11-15 19:23       ` Jorge Almeida
2016-11-15 19:32         ` Alan McKinnon
2016-11-15 19:45           ` Jorge Almeida
2016-11-16  2:10     ` [gentoo-user] " Walter Dnes
2016-11-16  7:23       ` Jorge Almeida
2016-11-16  9:08         ` Neil Bothwick
2016-11-16 11:25           ` Jorge Almeida
2016-11-16 20:51             ` Kai Krakow [this message]
2016-11-16 21:20               ` [gentoo-user] " Jorge Almeida
2016-11-17 20:42         ` [gentoo-user] " Frank Steinmetzger
2016-11-17 20:49           ` Jorge Almeida
2016-11-17 23:32             ` Frank Steinmetzger
2016-11-14 23:55   ` [gentoo-user] " Kai Krakow

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=20161116215129.0cdc0f02@jupiter.sol.kaishome.de \
    --to=hurikhan77@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