Skip to content
This repository has been archived by the owner on May 21, 2019. It is now read-only.

Allow to install using brew #175

Closed
vlad-shatskyi opened this issue Nov 9, 2015 · 10 comments
Closed

Allow to install using brew #175

vlad-shatskyi opened this issue Nov 9, 2015 · 10 comments

Comments

@vlad-shatskyi
Copy link
Contributor

No description provided.

@G07cha
Copy link
Contributor

G07cha commented Nov 9, 2015

As I know, first of all you need to release at least one version of application.
Also I would like to ask, what goal are you want to achieve by providing "brew formula"? It will be one of way to install "black-screen" or additional CLI tool?

@vlad-shatskyi
Copy link
Contributor Author

I think a brew cask should be the only way to install the application because it supports updates.

@G07cha
Copy link
Contributor

G07cha commented Nov 9, 2015

@ShockOne what about self-updater? It's more user-friendly.

@vlad-shatskyi
Copy link
Contributor Author

I don't think it is. There are certain benefits in having a single place to update your applications:

  • You don't need to think of each one separately
  • It doesn't ask you to update when you start the application with the intent to work and not to think about its new releases. I always have this experience with Firefox: I start it now and then to try something, and every time it asks me to update itself.

@G07cha
Copy link
Contributor

G07cha commented Nov 9, 2015

I start it now and then to try something, and every time it asks me to update itself.

This function can be disabled btw.

We don't need to do same as in Firefox, it can be just tiny button with text "Update available" that don't prevent using application at all or it can be just a background update.

@iiegor
Copy link
Contributor

iiegor commented Nov 9, 2015

// @alebcay

@vlad-shatskyi
Copy link
Contributor Author

Actually, since it's a terminal, it can update itself using brew, you know. :)

@alebcay
Copy link

alebcay commented Nov 9, 2015

Since it's an application bundle, I would encourage you to place it in Homebrew Cask, not homebrew, which is more geared for CLI stuff. As previously stated, you must push at least one built app bundle somewhere before we can add it (Homebrew Cask does not support building apps, unlike Homebrew). GitHub's releases functions will work just fine, if you feel that Black Screen is ready for primetime.

Homebrew Cask currently doesn't support automatic updates. Any update functionality must be handled by the application itself (for now, at least).

@vlad-shatskyi vlad-shatskyi added this to the 1.0 milestone Mar 10, 2016
@Nnubes256
Copy link

Nnubes256 commented May 22, 2016

Here's a working Cask template for 0.0.2:

cask 'black-screen' do
  version '0.0.2'
  sha256 'cbab7632af02ad276508e527118f161e9d76db01fe25a2114825b7a28f850a32'

  url "https://github.com/shockone/black-screen/releases/download/v#{version}/Black.Screen.zip"
  appcast "https://github.com/shockone/black-screen/releases.atom",
          checkpoint: 'd646b4da0c86a3c3a9471a75e8ae4a6e11f0bc5c084adcc5de9bdf0c8279cf39'
  name 'Black Screen'
  homepage 'https://github.com/shockone/black-screen'
  license :mit

  app 'Black Screen.app'
end

EDIT: oops I didn't notice this was a ~7 months old issue, sorry!

@vlad-shatskyi
Copy link
Contributor Author

brew cask install black-screen.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants