Earlier quoted context omitted.
> i'm not. all of it makes me nervous. even package managers with supposedly cryptographically secure verification make me nervous. Android and Chrome for example are really ahead of this in my opinion. Apps are sandboxed and you know uninstall clears up traces of them. Obviously it's not perfect but it's miles ahead of installation scripts and binary installers which can do anything they want with your system and mi…
> Apps are sandboxed and you know uninstall clears up traces of them. Not in all versions of Android, if they write stuff on the SD card.
Show HN: Swiss Army Knife for Mac OS X
61–67 of 67 posts
Re: Show HN: Swiss Army Knife for Mac OS X
#62Earlier quoted context omitted.
i'm not. all of it makes me nervous. even package managers with supposedly cryptographically secure verification make me nervous. but, you gotta do what you gotta do to actually do stuff. i sure as hell ain't going back to the days of compiling everything from source.
> i'm not. all of it makes me nervous. even package managers with supposedly cryptographically secure verification make me nervous. Android and Chrome for example are really ahead of this in my opinion. Apps are sandboxed and you know uninstall clears up traces of them. Obviously it's not perfect but it's miles ahead of installation scripts and binary installers which can do anything they want with your system and mi…
Re: Show HN: Swiss Army Knife for Mac OS X
#63Earlier quoted context omitted.
The basic command for keeping the machine awake is `caffeinate`, and has a few other nice options like changing what kind of sleep is prevented (disk, display, system) and also waiting on a PID (looks like that was added in 10.10). Related to that is `pmset -g assertions` which will list all the various things that are keeping your machine from sleeping.
strange, I always used `pmset noidle` instead of `caffeinate`. But seems it does the same. I somehow assumed `caffeinate` is the same as this app store thing called Caffeine.
Re: Show HN: Swiss Army Knife for Mac OS X
#64It’s not really clean, how it asks for /usr/local/m-cli to be added to $PATH but then litters that directory with other scripts.
INSTALL_DIR=$HOME/.m-cli sh Re: Show HN: Swiss Army Knife for Mac OS X
#65Does it need to be ran as root? Downloading m-cli from git to /usr/local fatal: could not create work tree dir '/usr/local/m-cli': Permission denied Failed to clone => https://github.com/rgcr/m-cli.git Off course it won't be able to access the /usr/local/
> You can also install it in a different path
INSTALL_DIR=$HOME/.m-cli sh
> Note: You need privilegesRe: Show HN: Swiss Army Knife for Mac OS X
#66Not sure I like the install method. I'm nervous of anything that asks me to pipe curl to shell.
Also not to like about the install method: The install.sh stores INSTALL_DIR in a variable but does not allow that variable to be overridden by the environment. So you're forced to install into /usr/local despite then being asked to add /usr/local/m-cli to your path. It would be better to allow /usr/local to be overridden so that installation doesn't require sudo. It's just as easy to add ~/.m-cli to your path.
Really? The documentation explicitly says that it does:
INSTALL_DIR=$HOME/.m-cli sh Re: Show HN: Swiss Army Knife for Mac OS X
#67Earlier quoted context omitted.
strange, I always used `pmset noidle` instead of `caffeinate`. But seems it does the same. I somehow assumed `caffeinate` is the same as this app store thing called Caffeine.
Using `pmset noidle` is now deprecated in favor of `caffeinate` according to the pmset man page.