Page 1 of 1

Filebot damaged after caskinstall

Posted: 27 Oct 2017, 18:11
by panda78
hi ,

i've purchased filebot from appstore but i need filebot CLI and i m trying to install with cask.
After cask installation i run "brew cask install filebot --force --appdir=/Applications"
after this cmd i found filebot in "usr/local/Caskroom/filebot/4.7.9" with denied symbol and if i run osx tell that it's possible to be damaged.
java is version 8

Code: Select all

filebot -script fn:sysinfo
FileBot 4.7.9 (r4984)
JNA Native: 5.1.0
MediaInfo: 0.7.93
7-Zip-JBinding: 9.20
Chromaprint: 1.4.2
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2017-05-15 (r500)
Groovy: 2.4.10
JRE: Java(TM) SE Runtime Environment 1.8.0_144
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 4 Core / 1 GB Max Memory / 14 MB Used Memory
OS: Mac OS X (x86_64)
Package: APP
uname: Darwin Batcomputer.local 17.0.0 Darwin Kernel Version 17.0.0: Thu Aug 24 21:48:19 PDT 2017; root:xnu-4570.1.46~2/RELEASE_X86_64 x86_64
Done ヾ(@⌒ー⌒@)ノ

thanks

Re: Filebot damaged after caskinstall

Posted: 27 Oct 2017, 19:27
by rednoah
The command-line call seems to be working just fine according to the log you posted. What's not working?

Re: Filebot damaged after caskinstall

Posted: 27 Oct 2017, 20:06
by panda78
command-line work fine but the standalone app not run . osx tell that the app could be damaged or incomplete .

im thinking to download paid version from apple store + cask version to run CLI. could be done?

Re: Filebot damaged after caskinstall

Posted: 28 Oct 2017, 00:09
by rednoah
Yes. If you want the GUI you'll need to use the App Store. If you want the CLI then you need to install via brew. If you want both GUI and CLI then you need to install via both App Store and brew. It's basically to separate independent things.

Re: Filebot damaged after caskinstall

Posted: 01 Feb 2018, 13:52
by devster
Installing the cask with your command probably overwrote or messed with the FileBot installed from the App Store.
My personal suggestion would be to install with --appdir=~/Applications which installs it in your home folder and avoids the conflict.

A hackish alternative would be to adapt the filebot.sh script to call the .jar installed by the AppStore, but I'm not even sure this is feasible.