Jens Noeckel wrote:
[]
So I think the best fix is to submit a new ghostscript.info file
which has the configure flag --without-jasper and then no longer
needs a BuildConflict entry.
I committed this to CVS. I also put you as new maintainer, as you said
you would accept(*). The revision
How about checking if the new data is the same as the old data - if
it is, then ignore the attempt to add duplicate data, if not, then die.
Or can you be *sure* that the data will always be the same?
Tim
On 2006-09-04, at 09:44 , [EMAIL PROTECTED]
wrote:
Message: 8
Date: Sun, 03 Sep 2006
Hi,
disabling jasper doesn't seem the right way to solve a buildconflict...
The -I/sw/include flags remain before the -I. flags, and since god
knows
what could be in /sw/include (eg, from a user's local pkgs), the
problem remains.
The first attempt, using the standard tools, worked
Benjamin Reed wrote:
I did some investigation of the node exists errors, and I think they are
completely bogus (at least, while I agree we shouldn't have gotten to
that point in the code path in the first place, I believe it is entirely
legal to ignore the error).
I've done some
On 04 Sep 2006, at 12:32, Martin Costabel wrote:
Benjamin Reed wrote:
I did some investigation of the node exists errors, and I think
they are
completely bogus (at least, while I agree we shouldn't have gotten to
that point in the code path in the first place, I believe it is
entirely
On Sep 4, 2006, at 12:26 AM, Martin Costabel wrote:
(*)One duty of the new maintainer might be to gently nudge the
maintainer of system-ghostscript to update it to 8.54, too ;-)
I've been tempted in the past to abolish system-tetex and system-
ghostscript from fink, and I'm tempted again at
Hello,
I tried to removed isfinite and isnan in gdl patch, as you suggested.
It compiles fine on 10.4, but fails on 10.3 because isfinite and isnan
are undefined (see the attached patch for 10.3 that Dominique sent
me).
I thought that isfinite and isnan were defined on both 10.3 and 10.4?
David R. Morrison wrote:
On Sep 4, 2006, at 12:26 AM, Martin Costabel wrote:
(*)One duty of the new maintainer might be to gently nudge the
maintainer of system-ghostscript to update it to 8.54, too ;-)
I've been tempted in the past to abolish system-tetex and system-
ghostscript from
On Sep 4, 2006, at 3:28 AM, Jean-François Mertens wrote:
Hi,
disabling jasper doesn't seem the right way to solve a
buildconflict...
The -I/sw/include flags remain before the -I. flags, and since god
knows
what could be in /sw/include (eg, from a user's local pkgs), the
problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2006, at 4:30 PM, Jens Noeckel wrote:
Logic then dictates that I should go even further and remove the
BuildDepends on libjpeg and libpng3, as well as the runtime
dependencies on the corresponding shlibs.
Of course, the whole point of
On Sep 4, 2006, at 1:40 PM, Chris Zubrzycki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2006, at 4:30 PM, Jens Noeckel wrote:
Logic then dictates that I should go even further and remove the
BuildDepends on libjpeg and libpng3, as well as the runtime
dependencies on
On 04 Sep 2006, at 23:36, Jens Noeckel wrote:
On Sep 4, 2006, at 1:40 PM, Chris Zubrzycki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2006, at 4:30 PM, Jens Noeckel wrote:
Logic then dictates that I should go even further and remove the
BuildDepends on libjpeg and
Am 04.09.2006 um 01:34 schrieb Alexander Hansen:
When trying an update-all after a selfupdate, this failed because
libjasper1 had to be removed – and it is too hard to ask my
permission? Even the package gets re-installed afterwards?
The engine isn't perfect--it will try to put the
On 9/4/06, Peter Dyballa [EMAIL PROTECTED] wrote:
Am 04.09.2006 um 01:34 schrieb Alexander Hansen:
When trying an update-all after a selfupdate, this failed because
libjasper1 had to be removed – and it is too hard to ask my
permission? Even the package gets re-installed afterwards?
-- Forwarded message --
From: yingcai zheng [EMAIL PROTECTED]
Date: Sep 4, 2006 12:47 AM
Subject: Re: [Fink-devel] db42-4.2.52-16 problem
To: Alexander Hansen [EMAIL PROTECTED]
Alexander Hansen wrote:
AKHsnip
Also: what version of the Xcode Tools are you using?
Dear Alexander,
On 9/4/06, Alexander Hansen [EMAIL PROTECTED] wrote:
-- Forwarded message --
From: yingcai zheng [EMAIL PROTECTED]
Date: Sep 4, 2006 12:47 AM
Subject: Re: [Fink-devel] db42-4.2.52-16 problem
To: Alexander Hansen [EMAIL PROTECTED]
Alexander Hansen wrote:
AKHsnip
Also:
There's a bug in (IIRC) math.h on gcc3.3 that causes those symbols to
be undefined in certain circumstances.
dan
On Mon, Sep 04, 2006 at 12:11:43PM -0400, S?bastien Maret wrote:
Hello,
I tried to removed isfinite and isnan in gdl patch, as you suggested.
It compiles fine on 10.4, but fails
17 matches
Mail list logo
