homebrew-cask/Casks/changes.rb

22 lines
832 B
Ruby
Raw Normal View History

2015-12-18 09:15:28 +08:00
cask 'changes' do
2015-11-04 05:55:56 +08:00
version '1.7.3'
sha256 '64fd2d6af3f3a85fb6d172d5e9bce15ae07d4b94de5b2360181445227bcc9c1a'
2016-02-12 06:10:22 +08:00
# bitbq_changes.s3.amazonaws.com was verified as official when first introduced to the cask
2015-07-12 18:45:34 +08:00
url "https://bitbq_changes.s3.amazonaws.com/changes-#{version}.zip"
2015-12-26 04:57:40 +08:00
appcast 'https://bitbq_changes.s3.amazonaws.com/changes-production.xml',
checkpoint: '524b59ed2fd0b0cb7829bfa7d4729769d169dc6e391a113550082d44fd831806'
2015-03-25 11:05:14 +08:00
name 'Changes'
homepage 'http://martiancraft.com/products/changes.html'
license :commercial
2014-09-16 00:05:22 +08:00
app 'Changes.app'
[WIP] Change artifact behavior to moving instead of symlinking (#13966) * Change app artifact to move instead of link First step towards change in installation behavior mentioned in [13201] * Fix handling of binaries linked from inside of app bundles Also adds `appdir` method for interpolation in stanzas * Change appdir to root Applications directory * Update 2-app tests * Refactor: add options, ivars to `Installer`, `Download` In preparation for upcoming changes, this commit cleans up some code. The commit includes: - In order to reduce unnecessary object passing, make both the `force` and `skip_cask_deps` option into instance variables of the `Installer` class - Introduce options hashes to initializers of both the `Installer` and `Download` class - When the `install --force` command enters the fetch phase, make it explicit in the code that fetching is never enforced in that case. - Update tests * Force overwrite artifacts on `--force` reinstall This commit changes the behavior of a `Moved` artifact such that if the target already exists, `brew cask install --force` will remove the existing target before moving the staged artifact. In that case, the warning message will say *overwriting* instead of *not moving*. The behavior of plain `brew cask install` remains unchanged; the same goes for the warning message for that case. * Change remaining artifacts to move instead of symlink * Update casks to use appdir in binary paths * Forcibly overwrite artifacts, modifying flags and using `sudo` if needed - This commit implements [the proposed behavior for `install --force`](https://github.com/caskroom/homebrew-cask/pull/13966#issuecomment-220830387) when a target already exists and has either permission problems or is not owned by the user. - The changes apply only when the `force` option is given. - Reused the existing safeguard from the `.pkg` artifact to prevent deleting important directories by bug or mistake - The two existing blacklists `SYSTEM_DIRS` and `UNDELETABLE_DIRS` have been consolidated into the `Hbc::MacOS` module. - `UNDELETABLE_DIRS` now also contains all the entries from `SYSTEM_DIRS` which was a to-do anyway. - The two blacklists are now also frozen for good measure. - The utility method `permissions_rmtree` was moved to `Hbc::Utils`. - The `tried_permissions` part in `Utils` now falls back correctly when there are also ownership issues at the same time. - Introduced a separate `current_user` method for mocking. - Added an optional feature to `FakeSystemCommand` so it can now act as a proxy to `SystemCommand`. - Added tests for various `permissions_rmtree` cases.
2016-06-01 03:23:21 +08:00
binary "#{appdir}/Changes.app/Contents/Resources/chdiff"
zap delete: [
'~/Library/Preferences/com.bitbq.Changes.plist',
'~/Library/Application Support/Changes',
'~/Library/Caches/com.bitbq.Changes',
]
2012-10-25 17:01:12 +08:00
end