So after a selfupdate and update-all, every bash shell I started up (/bin/bash, not some add-on) started spewing tons of garbage about syntax errors in function definitions that looked completion-related. Since I have a shell script called from my PROMPT_COMMAND, this happened every time I hit return.
I moved /sw/etc/profile.d/bash-completion.sh aside (changed the suffix from .sh to .DISABLED) and the problems disappeared. Now, if I get rid of my own .bashrc/.bash_profile and then load that bash-completion file, everything's fine, so it's some interaction with my personalized bash setup. Which is obviously not fink's responsibility. But I'm thinking that maybe the init.sh stuff is getting a little too fancy. There's no need to define completion for every command added by fink. I would expect /sw/bin/init.sh to be limited to putting /sw/bin in $PATH, and checking to see if it should add something to MANPATH (which it shouldn't if it's not already set), and likewise LD_LIBRARY_PATH, and then letting other package-specific scripts run to set up any other environment variables they need. Maybe make a separate script available to do other stuff like the bash completion, rather than having it automatically done by init.sh... It was just a little surprising to have my shell become effectively unusable after a fink update. -- Mark J. Reed <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
