[gentoo-dev] another global use flag...

[gentoo-dev] another global use flag...

[Carsten Lohrke]

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

use.local.desc:app-text/ghostscript-afpl:jasper - Enable support for jpeg2k 
(jasper)
use.local.desc:kde-base/kdegraphics:jpeg2k - Enable support for jpeg2k 
(jasper)
use.local.desc:kde-base/kdelibs:jpeg2k - Enable support for jpeg2k (jasper)
use.local.desc:net-proxy/ziproxy:jpeg2k - Enable support for jpeg2k (jasper)
use.local.desc:sci-libs/gdal:jasper - Adds support for JPEG 2000


I was just about adding another one and thought it would be better to merge 
them to a global jpeg2k use flag. Complains?


Carsten

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

Re: [gentoo-dev] another global use flag...

[Drake Wyrm]

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

Carsten Lohrke <carlo@gentoo.org> wrote:
> use.local.desc:app-text/ghostscript-afpl:jasper - Enable support for
> jpeg2k (jasper)
> use.local.desc:kde-base/kdegraphics:jpeg2k - Enable support for jpeg2k
> (jasper)
> use.local.desc:kde-base/kdelibs:jpeg2k - Enable support for jpeg2k
> (jasper)
> use.local.desc:net-proxy/ziproxy:jpeg2k - Enable support for jpeg2k
> (jasper)
> use.local.desc:sci-libs/gdal:jasper - Adds support for JPEG 2000
> 
> 
> I was just about adding another one and thought it would be better to merge 
> them to a global jpeg2k use flag. Complains?

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.

-- 
I used to think romantic love was a neurosis shared by two, a supreme
foolishness. I no longer thought that. There's nothing foolish in
loving anyone. Thinking you'll be loved in return is what's foolish.
  -- Rita Mae Brown

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

Re: [gentoo-dev] another global use flag...

[Carsten Lohrke]

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

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: 198 bytes --]

Re: [gentoo-dev] another global use flag...

[Meder Bakirov]

[-- 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 --]

Re: [gentoo-dev] another global use flag...

[Marcus D. Hanwell]

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

On Thursday 22 December 2005 21: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.
>
I second this sentiment - global use flags are supposed to be defined broadly 
so as to allow fairly generic easily understood terms. I know straight away 
what jpeg2k, but without looking at a description I have no idea what jasper 
is.

That is why I don't quite understand why Mozilla based browsers use the mozsvg 
use flag when there is already a global svg use flag available and if you 
enable svg you can pretty much guarantee you will want it in mozilla too. 
Users don't need to be bothered with the implementation details, if they want 
jpeg2k or svg support generally they are not going to be too concerned about 
which library provides it.

I also think jpeg2k should become a global use flag in answer to the original 
question :)

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

Re: [gentoo-dev] another global use flag...

[Mike Frysinger]

On Fri, Dec 23, 2005 at 02:03:39PM +0000, Marcus D. Hanwell wrote:
> That is why I don't quite understand why Mozilla based browsers use the mozsvg 
> use flag when there is already a global svg use flag available and if you 
> enable svg you can pretty much guarantee you will want it in mozilla too. 

maybe a bug ?  'mozsvg' has existed for much longer than 'svg' afaik
-mike
-- 
gentoo-dev@gentoo.org mailing list