Re: [Fink-devel] system-ghostscript8

2004-02-02 Thread Martin Costabel
Martin Costabel wrote: [] Unrecoverable error: rangecheck in get Operand stack: hrsyr.gsf0 This hrsyr.gsf is one of those Hershey fonts. If one removes the ghostscript-fonts part of the system-ghostscript8 package and installs the Fink ghostscript-fonts package, everything seems to

Re: [Fink-devel] disabling /usr/local/include

2004-02-02 Thread Alexander Hansen
On Feb 2, 2004, at 3:26 AM, Nigel Stanger wrote: On 1/2/2004 11:28 AM, David R. Morrison at [EMAIL PROTECTED] spake thus: I would appreciate feedback on this idea, both the mild version which affects only headers, and the more radical version which reimplements the change in order of library

Re: [Fink-devel] Translating man page?

2004-02-02 Thread Bertrand Lupart
He shouldn't need to. From the man man page: ... More, its man page seems to require the charset in the path: ...in the order of precedence: lang_country.charset lang.charset en.charset Have a look at fink's man or 10.3's, they should handle this better. Same man page as on 10.2.8,

Re: [Fink-devel] Re: disabling /usr/local/include

2004-02-02 Thread Peter O'Gorman
Matthias Neeracher wrote: I can see some value in disabling /usr/local/include (shouldn't we also disable /usr/local/lib ?), but I think putting %p/include and %p/lib at the end of our search paths rather than the beginning is going to cause us trouble: Wouldn't we be putting ourselves at the

[Fink-devel] Re: dists/10.2/stable/main/finkinfo/libs id3lib3.7-3.7.13-4.info,1.1,1.2

2004-02-02 Thread Christian Schaffner
Update of /cvsroot/fink/dists/10.2/stable/main/finkinfo/libs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6353/10.2/stable/main/ finkinfo/libs Modified Files: id3lib3.7-3.7.13-4.info Log Message: this has c++ code! There was already a GCC field in that info file, leading to

Re: [Fink-devel] Re: dists/10.2/stable/main/finkinfo/libs id3lib3.7-3.7.13-4.info,1.1,1.2

2004-02-02 Thread Benjamin Reed
Christian Schaffner wrote: There was already a GCC field in that info file, leading to WARNING: Field gcc occurs more than once in /sw/fink/dists/unstable/main/finkinfo/libs/id3lib4.info. Shall i remove it? yeah, i was a bit overzealous, I got an id3lib4 as well as 3.7 ;) Looks like it's

Re: [Fink-devel] Re: dists/10.2/stable/main/finkinfo/libs id3lib3.7-3.7.13-4.info,1.1,1.2

2004-02-02 Thread Christian Schaffner
On 02.02.2004, at 19:20, Benjamin Reed wrote: Christian Schaffner wrote: There was already a GCC field in that info file, leading to WARNING: Field gcc occurs more than once in /sw/fink/dists/unstable/main/finkinfo/libs/id3lib4.info. Shall i remove it? yeah, i was a bit overzealous, I got an

[Fink-devel] cyrus-sasl2-2.1.15-11 doesn't link against db 4.2

2004-02-02 Thread Blair Zajac
Hello, Trying the new cyrus-sasl2-2.1.15-11.info today and watching it compile, it doesn't try to link against Berkeley db 4.2. It'll pick up an older version from somewhere on your system, 4.1 or 4.0 depending upon what's installed. $ fink list db42-ssl Information about 2537 packages read in

Re: [Fink-devel] cyrus-sasl2-2.1.15-11 doesn't link against db 4.2

2004-02-02 Thread TheSin
the patch didn't apply on your system, -4.1 should be -4.2, what perl are you using? --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 2-Feb-04, at 1:15 PM, Blair Zajac wrote: checking for db.h... yes checking for db_create in -ldb-4.1... no checking

[Fink-devel] Re: cyrus-sasl2-2.1.15-11 doesn't link against db 4.2

2004-02-02 Thread Blair Zajac
TheSin wrote: it's not the patch, in the info file there is a patchscript which uses perl -pi ... inline replacement. and it should change all -4.1 to -4.2 Odd, not on my system: $ cd /sw/fink/10.3/unstable/crypto/finkinfo $ grep -i perl cyrus-sasl2.info This is $ head -5 cyrus-sasl2.info

[Fink-devel] Re: cyrus-sasl2-2.1.15-11 doesn't link against db 4.2

2004-02-02 Thread TheSin
scctually I just checked the dylib and it's not linking db at all. [EMAIL PROTECTED] [/sw/fink/dists/local/main/finkinfo]$ otool -L /sw/lib/libsasl2.2.0.15.dylib /sw/lib/libsasl2.2.0.15.dylib: /sw/lib/libsasl2.2.dylib (compatibility version 3.0.0, current version 3.15.0)

[Fink-devel] Re: cyrus-sasl2-2.1.15-11 doesn't link against db 4.2

2004-02-02 Thread TheSin
OH but I'm looking into it right now. I'll commit a new revision in a few minutes. Forgot to mention that. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 2-Feb-04, at 2:21 PM, Blair Zajac wrote: TheSin wrote: scctually I just checked the dylib

[Fink-devel] Re: cyrus-sasl2-2.1.15-11 doesn't link against db 4.2

2004-02-02 Thread TheSin
you have MUCH BIGGER issue if you have a .so --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 2-Feb-04, at 2:21 PM, Blair Zajac wrote: TheSin wrote: scctually I just checked the dylib and it's not linking db at all. [EMAIL PROTECTED]

[Fink-devel] Re: cyrus-sasl2-2.1.15-11 doesn't link against db 4.2

2004-02-02 Thread TheSin
OH I take that back, I see now it's a plugin, okay I have the fix, give me 5 minutes to test it. --- TS http://southofheaven.org Chaos is the beginning and end, try dealing with the rest. On 2-Feb-04, at 2:21 PM, Blair Zajac wrote: TheSin wrote: scctually I just checked the dylib and it's not

[Fink-devel] Re: dists/10.3/unstable/main/finkinfo/libs/perlmods getopt-long-pm.info,1.1,1.2 getopt-long-pm581.info,1.1,1.2

2004-02-02 Thread Daniel Macks
In gmane.os.apple.fink.cvs, you said: RCS file: /cvsroot/fink/dists/10.3/unstable/main/finkinfo/libs/perlmods/getopt-long-pm.info,v -Version: 2.34 +Version: 2.34_01 ^ Hello? You might want to take advantage of a Validation.pm with CVS r=1.98... dan -- Daniel Macks [EMAIL

Re: [Fink-devel] Re: dists/10.3/unstable/main/finkinfo/libs/perlmods getopt-long-pm.info,1.1,1.2 getopt-long-pm581.info,1.1,1.2

2004-02-02 Thread TheSin
damnit...it really doesn't affect anything other then I have to reversion things from their original versionswhy is this bad...can anyone tell, I did lots of test and dpkg doesn't give a crap about it. BTW Dan I'm not mad at you, just I don't agree with the limitation. --- TS