On Fri, Dec 23, 2005 at 02:03:39PM +, 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
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 nothi
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 appro
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-2
Carsten Lohrke <[EMAIL PROTECTED]> 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)
> us
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
