[MacPorts] #40603: MacPorts bash doesn't work properly as a default shell (should define SH_SOURCE_BASHRC)
MacPorts
noreply at macports.org
Sun Oct 13 03:40:50 PDT 2013
#40603: MacPorts bash doesn't work properly as a default shell (should define
SH_SOURCE_BASHRC)
----------------------+----------------------
Reporter: dlitz@… | Owner: raimue@…
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.2.0
Resolution: | Keywords:
Port: bash |
----------------------+----------------------
Comment (by raimue@…):
Replying to [comment:3 dlitz@…]:
> Right now, setting environment variables on OSX outside ~/.bashrc is a
pretty
> big mess[#ref2 (2)]. SSH_SOURCE_BASHRC is quite clean, in comparison,
and much more
> flexible.
I agree. The different environments often pose a problem.
> There's a reasonable argument that SSH_SOURCE_BASHRC is the wrong
approach to
> this problem in general. However, the fix is something that can only be
> properly solved by the OS vendor. The issue that Chet points out isn't
solved
> by having MacPorts bash behave differently from Apple bash: Programs on
OSX
> need to cope with the behavior of Apple bash anyway.
>
> So, despite the (valid) criticism of this approach in general, it would
still
> be better if MacPorts bash behaved the same Apple bash here, regardless
of what
> other distros do.
Yes, of course the compatibility with Apple's bash is important (although
it's quite old now). I meant I checked whether there are effects on other
tools we should be aware of. But so far, I did not experience any problem,
so I enabled this now in bash @4.2.45_2.
Committed in r112140.
--
Ticket URL: <https://trac.macports.org/ticket/40603#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list