Feature request: Auto-start a cask after installation about homebrew-bundle HOT 11 CLOSED

I think this first requires a way for brew to start a cask independently of brew bundle

from homebrew-bundle.

I think this first requires a way for brew to start a cask independently of brew bundle

did you mean for such a feature to be supported from the cmd-line brew first, and only then from the Brewfile's DSL?

from homebrew-bundle.

Yeah, since the Brewfile DSL just runs brew functions under the hood.

from homebrew-bundle.

I see various references to Bundle.system in this repo. I was thinking that would be the way to use the open command on macos to start the application. Wouldn't that suffice?

from homebrew-bundle.

But how does one start a cask. How do you know what to start?

from homebrew-bundle.

But how does one start a cask. How do you know what to start?

open command on macos like so: open /Applications/KeePassXC.app

from homebrew-bundle.

But a lot of casks are pkg files, or contain multiple apps. So that will create an experience where it's just a gamble if it'll work

from homebrew-bundle.

if that's the case, then my suggestion would be to let the user specify a system command to execute upon successful completion of the installation of each cask. That allows the flexibility to the user and they can choose to open 1 or more of those apps. Could we pivot to that?

from homebrew-bundle.

sorry, but I'm a 👎 on this feature request for a couple of reasons.

1. you don't "start" a cask. you install a cask which then extracts all the nessecary parts into your system. what you're talking about here is more related to services and being able to launch them. if you want this, I'd suggest looking at the individual cask/formula and seeing if it can be included in there. this is something that is already supported.
2. as @SMillerDev mentioned, a cask isn't always a single executable and expecting the user to know which they want to target is unreasonable. similarly, it's unreasonable for bundle to guess as getting the wrong information is worse than not doing it at all since you've then incorrectly taken the user down another path.

from homebrew-bundle.

I am likewise not in favor of this for the same reasons that Jacob is.

The at_exit method in a Brewfile should adequately handle this for your particular use case. at_exit runs just before the process exits for any reason as long as the process is still running. That is, it won't run if the process was killed. Within the bounds of the normal operation of brew bundle, at_exit should always run.

from homebrew-bundle.

Passing on this for now, sorry!

from homebrew-bundle.