[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bash 4.2 breaks source finding libs in lib/filename...
From: |
Greg Wooledge |
Subject: |
Re: bash 4.2 breaks source finding libs in lib/filename... |
Date: |
Wed, 29 Feb 2012 08:30:16 -0500 |
User-agent: |
Mutt/1.4.2.3i |
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.
- bash 4.2 breaks source finding libs in lib/filename..., Linda Walsh, 2012/02/28
- Re: bash 4.2 breaks source finding libs in lib/filename...,
Greg Wooledge <=
- Re: bash 4.2 breaks source finding libs in lib/filename..., Pierre Gaston, 2012/02/29
- Re: bash 4.2 breaks source finding libs in lib/filename..., Linda Walsh, 2012/02/29
- Re: bash 4.2 breaks source finding libs in lib/filename..., Eric Blake, 2012/02/29
- Re: RFE: allow bash to have libraries (was bash 4.2 breaks source finding libs in lib/filename...), Linda Walsh, 2012/02/29
- Re: RFE: allow bash to have libraries (was bash 4.2 breaks source finding libs in lib/filename...), John Kearney, 2012/02/29
- Re: RFE: allow bash to have libraries (was bash 4.2 breaks source finding libs in lib/filename...), Mike Frysinger, 2012/02/29