[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Fab-user] OS X and fabric.contrib.files.exists
From: |
Jeff Forcier |
Subject: |
Re: [Fab-user] OS X and fabric.contrib.files.exists |
Date: |
Mon, 1 Jun 2009 19:02:34 -0400 |
2009/6/1 Niklas Lindström <address@hidden>:
> Hi again,
>
> I just noticed that `fabric.contrib.files.exists` doesn't work on OS
> X, due to the "--color" flag. Is that a necessary precaution for some
> systems, or could it be removed altogether?
A number of things in the contrib.* files are unlikely to be fully
portable right now, unfortunately, since they're still largely based
on stuff I wrote for my own environment.
I'd like to make them moreso (I'd also like to put in ANSI color
stripping so passing --color=never isn't necessary) but for now, if I
take that flag out it won't work for me or anyone else with color 'ls'
enabled on the remote end, so it becomes a "who to inconvenience" game
with color 'ls' folks vs non-GNU-ls ones :)
We could put in a stopgap solution which checks system type and omits
the --color if it doesn't appear to be Linux, e.g. "if run('uname -s')
!= 'Linux'". I've done this in my dotfiles for similar reasons, with
some success.
-Jeff