public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Meder Bakirov <bakirov@transfer.kg>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] another global use flag...
Date: Fri, 23 Dec 2005 11:28:30 +0600	[thread overview]
Message-ID: <200512231128.39693.bakirov@transfer.kg> (raw)
In-Reply-To: <200512222252.16007.carlo@gentoo.org>

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

I, as a regular user, second this.

Before we had a 'bzlib' USE-flag, and now it is 'bzip2', which is more 
user-friendlier for users to understand. 

On Friday 23 December 2005 03:52, Carsten Lohrke wrote:
> On Thursday 22 December 2005 20:14, Drake Wyrm wrote:
> > Query: Which would be more appropriate in this case? "jasper" for the
> > library it pulls in as a depend, or "jpeg2k" for the functionality that
> > library provides? There's nothing else in the tree (as far as I can
> > tell) which provides JPEG-2000, but there could be.
>
> It is imho a _problem_ when use flags are _unnecessarily_ named after the
> library instead the provided functionality. When there are two libs doing
> the same thing, a single use flag should suffice: Less use flags mean
> reduced complexity for the user, who likely will understand what "jpeg2k"
> means, but not "jasper". Which leads me to the next issue; Often you can
> read:
>
> foo - enables support for $category/foo
>
> Such a description is as good as none. To give a sample how it should be:
>
> jpeg2k - Support for JPEG 2000, a wavelet-based image compression format.
>
>
> Carsten

-- 
С уважением,

Медер Бакиров

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-23  5:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 16:10 [gentoo-dev] another global use flag Carsten Lohrke
2005-12-22 19:14 ` Drake Wyrm
2005-12-22 21:52   ` Carsten Lohrke
2005-12-23  5:28     ` Meder Bakirov [this message]
2005-12-23 14:03     ` Marcus D. Hanwell
2005-12-23 14:12       ` Mike Frysinger

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=200512231128.39693.bakirov@transfer.kg \
    --to=bakirov@transfer.kg \
    --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