Possible good news on the environment-variables front

[Jamis Buck]

Alright, I have no idea why I never picked up on this before. If you
already knew this and tried to tell me, I apologize for my obtuseness.

Apparently, the reason Capistrano doesn't pick up your .bashrc and
such is because Capistrano allocates a pseudo-tty for each command.
I'm not sure why I made it do that. However, if I take that particular
code out, the .bashrc gets executed for each command, and (as far as
my ad-hoc testing goes) it looks like everything still works...

I'm going to play with it a bit more, and if I don't find any
compelling reason to do otherwise, I'm going to add an option which
allows you to explicitly ask for a pty if you need one. The default
will be no pty, and hopefully that will be the end of all the grief
about Capistrano not reading your login environment.

(If any of you happen to have more info about this than I have, I'd
appreciate your comments!)

- Jamis

[Joe]

Jamis,

Do you have a patch available for this, if not the updated gem? I'm
seeing some strange errors with rubygems that crop up only with
capistrano remote tasks (even with trying to source .bashrc manually).

Thanks,
Joe

[Jamis Buck]

No patch yet, unfortunately. I'm completely focused on getting
net-ssh, net-scp, and net-sftp out the door right now, and when
they're ready I'll get back on capistrano. Sorry this is taking so
long--no one wants it done more than I do. :(

- Jamis

[Joe]

No problem, I was able to work around the issue. Don't worry - I
appreciate all of your hard work on this great set of tools.

On Aug 22, 10:33 pm, "Jamis Buck" <ja...@37signals.com> wrote:
> No patch yet, unfortunately. I'm completely focused on getting
> net-ssh, net-scp, and net-sftp out the door right now, and when
> they're ready I'll get back on capistrano. Sorry this is taking so
> long--no one wants it done more than I do. :(
>
> - Jamis
>