I'm all for changing tools to something more reliable and more cross-platform. Thinking about the common user, not a dev -- we could fork just to package it as a npm module mainly for users to easily install it (since we require npm anyway) that way they can avoid another dependency.
Not sure if this extra effort to npm package is worth it, if users want this feature installing homebrew wouldn't be too much of a hassle, but it may be a barrier for some. On Tue, Apr 22, 2014 at 11:40 AM, Andrew Grieve <agri...@google.com> wrote: > Shaz, wondering if you looked into using libimobiledevice instead of > ios-deploy. Seems like it's much more capable, works on Linux, and > well-maintained. > > http://www.libimobiledevice.org/ > > There are "idevice*" commands that match ios-deploy: > > `idevice_id -l` to list attached devices > `ideviceinstaller` to install/uninstall/list apps > `ideviceimagemounter` to mount the dev image > `idevice-app-runner` to launch an app > `idevicedebugserverproxy` to debug via lldb > > plus commands to: > > `ideviceinfo` to get device info > `idevicefs` to list/copy files to/from devices > `idevicesyslog` to tail the syslog > ... etc ... > > Only downside I can see is that for OSX, installing is a bit of a > pain. There's a brew package for ideviceinstaller, but not the other > tools. This random page worked for me: > https://github.com/bitbar/libimobiledevice-binaries, but we might want > something better... >
