public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hanno Böck" <hanno@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Removing barely used global flags
Date: Tue, 23 Oct 2018 10:25:09 +0200	[thread overview]
Message-ID: <20181023102509.0636d41c@computer> (raw)
In-Reply-To: <1540032063.1292.6.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

On Sat, 20 Oct 2018 12:41:03 +0200
Michał Górny <mgorny@gentoo.org> wrote:

> We seem to have a lot of global flags that are used only by a few
> packages.  How about moving them to local flags?  List of flags with
> less than 5 packages using them, ordered by use count, follows.  Where
> applicable, local flag descriptions are listed.

No disagreement in principle, however it might be worth checking which
of them are practically used at all or could be removed entirely.

"directfb" caught my attention, which I doubt is very active today.
Though the package in question - libggi - only uses the directfb flag
in an old ebuild, the latest one hard-disables directfb.
So well, if you stabilize libggi-2.2.2-r1 and remove the old ebuild you
can entirely get rid of this useflag instead of making it local.

Plausibly there may be other such cases, i.e. flags that were used in
the past, but for things that got deprecated / out of fashion / are
practically no longer used.

-- 
Hanno Böck
https://hboeck.de/

mail/jabber: hanno@hboeck.de
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2018-10-23  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 10:41 [gentoo-dev] [RFC] Removing barely used global flags Michał Górny
2018-10-20 10:54 ` Kent Fredric
2018-10-22 14:53 ` James Le Cuirot
2018-10-23  8:25 ` Hanno Böck [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=20181023102509.0636d41c@computer \
    --to=hanno@gentoo.org \
    --cc=gentoo-dev@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