> Spotlight does not touch *.build directories. That's why fink.build was
> introduced in the first place. Maybe the people who have this weird
> error changed their build directory to something other than fink.build?

Martin,
        Ahhh... [me: starts renaming all his project build directories]
My Spotlight blacklist added the fink/src tree before fink.build was
introduced, so I supposed I don't need that anymore.  Good to know.

However, I didn't rename the fink.build directory on either of my test
systems, so that still doesn't explain the gcc42 packaging-failure I
reproduced (10.4, Intel, tar-1.16.1-1).  I hope we figure this out
eventually.

Fang



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to