On 6 May 2002, tom keyes wrote:
> On Sat, May 4, 2002 3:06 PM, Alexander Strange <[EMAIL PROTECTED]> wrote:
>
> >This script should fix the null file problems:
> >
> >#!/bin/sh
> >rm /sw/bin/{tar,gzip,gunzip}
> >ln -s /usr/bin/gzip /sw/bin/gzip
> >ln -s /usr/bin/gunzip /sw/bin/gunzip
> >ln -s /usr/bin/gnutar /sw/bin/tar
>
> Hmmm - why does fink has its own versions of the utlities?
Fink offers alternate versions of these utilities in the fileutils package
(which isn't just a Fink thing -- I've also seen versions of it for Linux
and Windows).
> I got the same error message when I tried to unpack fink-09.11.tar.gz by
> hand but when as zorro suggested I downloaded fink-09.11.tar.gz and
> untarred it by hand everything worked. Wouldn't that suggest the problem
> was in the download, or is a file downloaded by fink automatically
> flaggged to use the fink utilities?...tom.
Well, partly that depends on your $PATH -- if you have /sw ahead of other
trees, then the Fink stuff will be called over anything else. OTOH if you
put /sw last, then you'll still have the system version as the default.
Really, now that I think about it, is it at all necessary to symlink files
from /usr/bin to /sw/bin? It's a safe assumption that almost everyone has
/usr/bin in their path, so duplicating the pointer in /sw shouldn't be
necessary for anyone, should it? If the versions in /sw are corrupted,
then so be it -- just delete them. I don't think you need to go the extra
step & symlink them to restore functionality.
--
Chris Devers [EMAIL PROTECTED]
Apache / mod_perl / http://homepage.mac.com/chdevers/resume/
"More war soon. You know how it is." -- mnftiu.cc
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
