Re: bash 4.2 breaks source finding libs in lib/filename...

[Pierre Gaston]

On Wed, Feb 29, 2012 at 3:30 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> On Tue, Feb 28, 2012 at 05:34:21PM -0800, Linda Walsh wrote:
>> How can one get the same behavior as before and look up files
>> relative to PATH regardless of them having a '/' in them?
>
> What?  That sounds like it WAS a bug before, and you had somehow
> interpreted it as a feature.  And now you're asking to have the bug
> back.
>
> Any pathname that contains a / should not be subject to PATH searching.
>

Not sure which version supported that:

$ echo $BASH_VERSION;mkdir -p foo/bar; echo echo foo
foo/bar/file;PATH=$PWD/foo:$PATH;source bar/file;source foo/bar/file
2.05b.0(1)-release
bash2: bar/file: No such file or directory
foo

$ echo $BASH_VERSION;mkdir -p foo/bar; echo echo foo>
foo/bar/file;PATH=$PWD/foo:$PATH;source bar/file;source foo/bar/file
3.2.25(1)-release
-bash: bar/file: No such file or directory
foo

$ echo $BASH_VERSION;mkdir -p foo/bar; echo echo foo
foo/bar/file;PATH=$PWD/foo:$PATH;source bar/file;source foo/bar/file
4.0.33(1)-release
bash4: bar/file: No such file or directory
foo