Oh no, "UNCLE" FINK DIED!?!!!?!?!?!! Why didn't anyone tell me...
;-) ck
On Tuesday, January 21, 2003, at 06:56 pm, ismaila shidaku wrote:
Hello,
I am Barrister Ismaila Shidaku an attorney to late MARK FINK an
Immigrant, who was a business man/contractor in Nigeria with the
NIGERIAN NATI
Hello,
I am Barrister Ismaila Shidaku an attorney to late MARK FINK an Immigrant, who was a
business man/contractor in Nigeria with the NIGERIAN NATIONAL PETROLEUM CORPORATION
(NNPC) Here in after shall be referredto as my client.On the 30th of march 2002, my
client,his wife and their threech
On Tuesday, January 21, 2003, at 11:48 AM, David wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello guys.
Fink.fm is available and even though we are no radio station I am
short of registering it. It would be a 200 dollar Investment for the
next two years which I am well willing
On Tuesday, January 21, 2003, at 01:46 PM, Ben Hines wrote:
erlmodules.info
Package: system-perlmodules
Version: 1.0
Provides: gd-pm, algorithm-diff-pm, http-dav-pm (parse the
package names from the output of "fink list --section=perlmods -w=200"
and put them all here)
Type: nosource
Com
On Monday, January 20, 2003, at 04:45 AM, Randal L. Schwartz wrote:
Any thoughts on how to do this without breaking everything open?
With the current fink, the way to make a system-* package would be:
filename: system-perlmodules.info
Package: system-perlmodules
Version: 1.0
Provides: gd-p
Ben Hines wrote:
Dan't blame CPAN, but Apple with their crappy HFS+, for that...
I expericenced, the same problem, of course :-}
No, DO blame CPAN. Why are they putting stuff in /usr/bin ? That is for
vendor supplied things in any case.
Agtually, blame Apple. Apple's perl is configured to p
On Tuesday, January 21, 2003, at 11:57 AM, Xavier HUMBERT wrote:
[EMAIL PROTECTED] (Hisashi T Fujinaka) wrote :
it puts things places I don't want
(overwriting /usr/bin/head, for example)
Dan't blame CPAN, but Apple with their crappy HFS+, for that...
I expericenced, the same problem, of c
[EMAIL PROTECTED] (Hisashi T Fujinaka) wrote :
> it puts things places I don't want
> (overwriting /usr/bin/head, for example)
Dan't blame CPAN, but Apple with their crappy HFS+, for that...
I expericenced, the same problem, of course :-}
--
Xavier
http://www.freetibet.org
http://www.tibet.fr/
Seems vitriolic.
It looked like there was some confusion with respect to the cause of the
problem, so I posted a clarification including the imlib version
numbers.
On Tue, 2003-01-21 at 13:38, David R. Morrison wrote:
> In case anyone wants to follow the thread over at macosxhints forum, here
> i
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Dienstag, Jänner 21, 2003, at 07:42 Uhr, Benjamin Reed wrote:
Ah, you're right. So build-deps are the only way to handle this. So
I guess the question is, do we upgrade everything to use libpng3? Or
do we downgrade to libpng?
David R. Morrison wrote:
My understanding from earlier discussions is that if you have imlib installed
and build a package which uses imlib-config, then -lpng is inserted into
your link line. Since libpng and libpng3 both use libpng.dylib, the
thing the resulting binary is linked to depends on wh
In case anyone wants to follow the thread over at macosxhints forum, here
it is:
http://forums.macosxhints.com/showthread.php?s=&postid=43170#post43170
---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training?
My understanding from earlier discussions is that if you have imlib installed
and build a package which uses imlib-config, then -lpng is inserted into
your link line. Since libpng and libpng3 both use libpng.dylib, the
thing the resulting binary is linked to depends on which version of
libpng was
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Dienstag, Jänner 21, 2003, at 07:22 Uhr, David R. Morrison wrote:
Sure. The problem is, how do we trigger the upgrade? We need to make
sure
that everything is *rebuilt* after upgrading, right? So does this mean
a versioned depende
David R. Morrison wrote:
Sure. The problem is, how do we trigger the upgrade? We need to make sure
that everything is *rebuilt* after upgrading, right? So does this mean
a versioned dependency on anything linked against imlib, for example?
I'm not sure that's the case. Since the deps are all
Sure. The problem is, how do we trigger the upgrade? We need to make sure
that everything is *rebuilt* after upgrading, right? So does this mean
a versioned dependency on anything linked against imlib, for example?
-- Dave
P.S. I added a message to users, inspired by this situation, to Fink
David R. Morrison wrote:
OK, we have a pretty serious problem here.
As some of you know, it began with kde, where it was discovered that compiling
kde with libpng3 led to runtime problems apparently caused by imlib not
having been updated to libpng3.
So someone updated imlib to libpng3, and now
OK, we have a pretty serious problem here.
As some of you know, it began with kde, where it was discovered that compiling
kde with libpng3 led to runtime problems apparently caused by imlib not
having been updated to libpng3.
So someone updated imlib to libpng3, and now gnome users are having tre
From: Thomas Thatcher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Hi Dave,
An avid fink user in the MacOSX Hints forum has reported an unusual
problem this morning. I wonder if you might know anything about it
since the cvs update for this morning installed new versions of libpng
which is supp
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello guys.
Fink.fm is available and even though we are no radio station I am short
of registering it. It would be a 200 dollar Investment for the next two
years which I am well willing to make. The question is, would you all
accept this as an
Hello.
Some might know, that I currently try to improve the PR, look and
feel and Documentation of Fink.
Thus I am trying to gather a few ideas and contributions to enhance the
website and documentation in the future.
If you are someone involved with graphic
design or an artsy person, please
21 matches
Mail list logo
