Re: Help wanted from Mojave users

[Andrew Janke]

On 5/23/21 1:15 AM, Joshua Root wrote:
> On 2021-5-23 14:53 , Andrew Janke wrote:
>>
>> I have a 10.14.6 VM running Xcode 11.3.1 prepped to test this; results
>> coming soon.
>
> Thank you.
>
>> Minor issue while trying to find a MacPorts 2.6.4 installer: The "our
>> packaged downloads" link in the "Installing MacPorts" section of
>> https://www.macports.org/install.php, pointing to
>> https://github.com/macports/macports-base/releases/download/v2.7.0/, is
>> 404. Is this just because the 2.7.0 release has been yanked or
>> something? Or maybe GitHub has changed the URL pattern here?
>
> Fixed, thanks for pointing it out. 2.7.0 has not been yanked (the
> binary installer for 10.14 was built against the 10.14 SDK and so
> doesn't suffer from the issue.)
>
> - Josh
I think my test was successful; please see Trac for details. Please let
me know if I need to change the test process at all; this is my first
time installing MacPorts from source.

Cheers,
Andrew

Re: Help wanted from Mojave users

[Joshua Root]

On 2021-5-23 14:53 , Andrew Janke wrote:


I have a 10.14.6 VM running Xcode 11.3.1 prepped to test this; results
coming soon.


Thank you.


Minor issue while trying to find a MacPorts 2.6.4 installer: The "our
packaged downloads" link in the "Installing MacPorts" section of
https://www.macports.org/install.php, pointing to
https://github.com/macports/macports-base/releases/download/v2.7.0/, is
404. Is this just because the 2.7.0 release has been yanked or
something? Or maybe GitHub has changed the URL pattern here?


Fixed, thanks for pointing it out. 2.7.0 has not been yanked (the binary 
installer for 10.14 was built against the 10.14 SDK and so doesn't 
suffer from the issue.)


- Josh

Re: Help wanted from Mojave users

[Andrew Janke]

On 5/22/21 11:08 PM, Joshua Root wrote:
> Could someone with a 10.14 system running an Xcode version that
> defaults to building against the 10.15 SDK please try installing the
> tip of the release-2.7 branch on top of a MacPorts 2.6.4 installation?
> Report the results in the comments here:
> 
>
> A speculative fix has been checked in, but it has yet to be confirmed
> to fix the issue by someone who experienced it "in the wild". I'd like
> to get a new release with the fix onto rsync ASAP so nobody else
> selfupdates to a broken state, but confirmation of the fix is needed
> first.
>
> - Josh

I have a 10.14.6 VM running Xcode 11.3.1 prepped to test this; results
coming soon.

Minor issue while trying to find a MacPorts 2.6.4 installer: The "our
packaged downloads" link in the "Installing MacPorts" section of
https://www.macports.org/install.php, pointing to
https://github.com/macports/macports-base/releases/download/v2.7.0/, is
404. Is this just because the 2.7.0 release has been yanked or
something? Or maybe GitHub has changed the URL pattern here?

I think I found the 2.6.4 installer by going to
https://github.com/macports/macports-base/releases/ instead.

Cheers,
Andrew

Help wanted from Mojave users

[Joshua Root]

Could someone with a 10.14 system running an Xcode version that defaults 
to building against the 10.15 SDK please try installing the tip of the 
release-2.7 branch on top of a MacPorts 2.6.4 installation? Report the 
results in the comments here:



A speculative fix has been checked in, but it has yet to be confirmed to 
fix the issue by someone who experienced it "in the wild". I'd like to 
get a new release with the fix onto rsync ASAP so nobody else 
selfupdates to a broken state, but confirmation of the fix is needed first.


- Josh

Re: iTerm2 Question

[Ryan Schmidt]

On May 22, 2021, at 17:21, Jason Liu wrote:

> If I'm not mistaken, to get a .app to show up in the /Applications/MacPorts 
> folder, you need to place the .app into ${destroot}$prefix/Applications at 
> some point during the destroot phase.

If the build system does not install the app for you, you can do it manually by 
overriding the destroot phase. In that case the correct location to copy it to 
is ${destroot}${applications_dir}.

Re: iTerm2 Question

[Jason Liu]

If I'm not mistaken, to get a .app to show up in the /Applications/MacPorts
folder, you need to place the .app into ${destroot}$prefix/Applications at
some point during the destroot phase.

-- 
Jason Liu


On Sat, May 22, 2021 at 5:07 PM Mark Anderson  wrote:

> So I can get iTerm2 to build correctly using Xcode 1.0 portgroup which
> solves a lot of the makefile problems, but I'm unsure what to do for the
> destroot phase to drop the .app into /Application/Macports. Any help would
> be appreciated.
>
> —Mark
> ___
> Mark E. Anderson 
> MacPorts Trac WikiPage 
> GitHub Profile 
>
>

Re: Publicizing MacPorts [installation]

[Bjarne D Mathiesen]

Joshua Root wrote:
> I think the best thing we could do to facilitate one-liner command line
> installation is set up a redirect so you can download the latest binary
> installer for your OS version without having to construct its
> not-so-easy-to-derive name yourself. It would then be simple to download
> the .pkg and feed it to installer(8).

so ... do we want to have a HomeBrew like instaler option ?

And if so : what type ? My solution installs directly from source & thus
by-passes the problem of finding the correct .pkg.

My complete script furthermore establishes a basis for maintainance (it
needs more --help options, but that can be fixed)

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
OpenCore + macOS 10.15.7 Catalina
MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
ATI Radeon RX 590 8 GB

iTerm2 Question

[Mark Anderson]

So I can get iTerm2 to build correctly using Xcode 1.0 portgroup which
solves a lot of the makefile problems, but I'm unsure what to do for the
destroot phase to drop the .app into /Application/Macports. Any help would
be appreciated.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage 
GitHub Profile 

Re: Publicizing MacPorts [installation]

[Bjarne D Mathiesen]

Joshua Root wrote:
> On 2021-5-23 03:12 , Bjarne D Mathiesen wrote:
>>
>>
>> Artem Loenko wrote:
>>> Yes, thanks for the tips! I am pretty sure that it is possible to
>>> automate it one way or another. But my point is that it would be
>>> helpful to have a one-liner to install MacPorts and maintain it as a
>>> part of the main repository.
>>>
>>
>> I'm 90% there there with this :
>> /usr/bin/env bash -c $( curl -fsSL --url
>> 'https://trac.macports.org/raw-attachment/wiki/howto/AdvancedDailyAdm/macports.bash'
>>
>> ) install
>>
>> When I'm running this as my normal un-privileged user,
>> it executes 邏 (and fails because it's un-privileged)
>>
>> !!! but !!! if I try this as my admin user, nothing happens 樂邏
>> There's some obscure security setting I presently can't fathom, because
>> I can run the script locally (without curl) without any issues. And it
>> does download - it just doesn't execute 樂邏樂
> 
> That's probably Gatekeeper and/or the Quarantine attribute doing its
> thing and stopping you from running arbitrary code straight from the
> web. curl | sh or the equivalent should be considered an antipattern

And yet HomeBrew uses it.

Now, how do I go about solving my original problem / finding the root
cause ?!?

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
OpenCore + macOS 10.15.7 Catalina
MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
ATI Radeon RX 590 8 GB

Re: Publicizing MacPorts [installation]

[Jason Liu]

On Sat, May 22, 2021 at 1:35 PM Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
>
> Yes, thanks for the tips! I am pretty sure that it is possible to automate
>> it one way or another. But my point is that it would be helpful to have a
>> one-liner to install MacPorts and maintain it as a part of the main
>> repository.
>
>
> This was of course suggested years ago as well, when homebrew first did
> it, but at that time was that it was both not needed and not a useful
> addition to MacPorts, if I recall the full email exchange correctly, so we
> let the idea die.
>

I feel like having a one-liner to install MacPorts, similar to Homebrew,
would be incredibly useful, especially for people who are not tech savvy.
It seems that many of us on the mailing list, including myself, already
have our own home-grown scripts to automate installing MacPorts. One thing
that I particularly like about the Homebrew installer is that it
automatically installs the CLT... I've been doing something similar in my
own MacPorts install script for around a decade.

My script even automatically accepts the Xcode license by using a small
chunk of expect. I realize that from the perspective of the MacPorts
developers, we might not want to be taking over control of this step from
the user. But from personal experience as a sysadmin, even this seemingly
minor step can be a fairly high hurdle for people who are not tech savvy.

Another thing that my script tries to automate is to add /opt/local to
everyone's $PATH if the script detects that SIP is disabled.

On Sat, May 22, 2021 at 2:31 PM Joshua Root  wrote:

>
> I think the best thing we could do to facilitate one-liner command
> line installation is set up a redirect so you can download the latest
> binary installer for your OS version without having to construct
> its not-so-easy-to-derive name yourself. It would then be simple to
> download the .pkg and feed it to installer(8).
>

This would be incredibly useful, and would allow me to cut out around 40-50
lines of code from my MacPorts install script (which is currently
constructing the not-so-easy-to-derive name myself). A single permalink
redirect would also allow the installation instructions to be simplified on
the MacPorts website, instead of what's currently there:

3. Install MacPorts for your version of the operating system:
* macOS Big Sur v11

* macOS Cataline v10.15

* macOS Mojave v10.14

* Older OS? See here. 

-- 
Jason Liu


On Sat, May 22, 2021 at 1:35 PM Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

> > Yes, thanks for the tips! I am pretty sure that it is possible to
> automate it one way or another. But my point is that it would be helpful to
> have a one-liner to install MacPorts and maintain it as a part of the main
> repository.
>
> This was of course suggested years ago as well, when homebrew first did
> it, but at that time was that it was both not needed and not a useful
> addition to MacPorts, if I recall the full email exchange correctly, so we
> let the idea die.
>
> I wrote up a MacPorts install script for Jeremy’s Xquartz project here <
> https://github.com/XQuartz/XQuartz/blob/master/install-or-update-macports.sh>
> that adds a bit more trickery he needed, but the basic guts was extremely
> simple and what I recommend to people who complain that MacPorts is
> extremely difficult to get installed and they claim to have spent hours and
> hours and hours trying to make it work:
>
> ==
>
> cd /tmp
> git clone -b release-2.7 https://github.com/macports/macports-base.git
> cd macports-base
> ./configure && make && sudo make install
>
>
> and then add to the $PATH as usual
>
> ==

Re: Publicizing MacPorts [installation]

[Joshua Root]

On 2021-5-23 03:12 , Bjarne D Mathiesen wrote:



Artem Loenko wrote:

Yes, thanks for the tips! I am pretty sure that it is possible to automate it 
one way or another. But my point is that it would be helpful to have a 
one-liner to install MacPorts and maintain it as a part of the main repository.



I'm 90% there there with this :
/usr/bin/env bash -c $( curl -fsSL --url
'https://trac.macports.org/raw-attachment/wiki/howto/AdvancedDailyAdm/macports.bash'
) install

When I'm running this as my normal un-privileged user,
it executes 邏 (and fails because it's un-privileged)

!!! but !!! if I try this as my admin user, nothing happens 樂邏
There's some obscure security setting I presently can't fathom, because
I can run the script locally (without curl) without any issues. And it
does download - it just doesn't execute 樂邏樂


That's probably Gatekeeper and/or the Quarantine attribute doing its 
thing and stopping you from running arbitrary code straight from the 
web. curl | sh or the equivalent should be considered an antipattern (at 
one point there was even a tumblr hall of shame for it.)


I think the best thing we could do to facilitate one-liner command line 
installation is set up a redirect so you can download the latest binary 
installer for your OS version without having to construct its 
not-so-easy-to-derive name yourself. It would then be simple to download 
the .pkg and feed it to installer(8).


- Josh

Re: Publicizing MacPorts [installation]

[Ken Cunningham]

> Yes, thanks for the tips! I am pretty sure that it is possible to automate it 
> one way or another. But my point is that it would be helpful to have a 
> one-liner to install MacPorts and maintain it as a part of the main 
> repository. 

This was of course suggested years ago as well, when homebrew first did it, but 
at that time was that it was both not needed and not a useful addition to 
MacPorts, if I recall the full email exchange correctly, so we let the idea die.

I wrote up a MacPorts install script for Jeremy’s Xquartz project here 
 
that adds a bit more trickery he needed, but the basic guts was extremely 
simple and what I recommend to people who complain that MacPorts is extremely 
difficult to get installed and they claim to have spent hours and hours and 
hours trying to make it work:

==

cd /tmp
git clone -b release-2.7 https://github.com/macports/macports-base.git
cd macports-base
./configure && make && sudo make install


and then add to the $PATH as usual

==

Re: Publicizing MacPorts [installation]

[Bjarne D Mathiesen]

Artem Loenko wrote:
> Yes, thanks for the tips! I am pretty sure that it is possible to automate it 
> one way or another. But my point is that it would be helpful to have a 
> one-liner to install MacPorts and maintain it as a part of the main 
> repository.
> 

I'm 90% there there with this :
/usr/bin/env bash -c $( curl -fsSL --url
'https://trac.macports.org/raw-attachment/wiki/howto/AdvancedDailyAdm/macports.bash'
) install

When I'm running this as my normal un-privileged user,
it executes 邏 (and fails because it's un-privileged)

!!! but !!! if I try this as my admin user, nothing happens 樂邏
There's some obscure security setting I presently can't fathom, because
I can run the script locally (without curl) without any issues. And it
does download - it just doesn't execute 樂邏樂

but the following is presently a more complete solution, that also
provides the script for further use.

#!/usr/bin/env bash

declare
baseURL='https://trac.macports.org/raw-attachment/wiki/howto/AdvancedDailyAdm'

mkdir -p MacPorts
cd MacPorts
curl -O --url "${baseURL}/portDefaults"
curl -O --url "${baseURL}/macports.bash"
chmod +x *.bash
sudo macports.bash setpaths
sudo macports.bash install
macports.bash --help


-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
OpenCore + macOS 10.15.7 Catalina
MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
ATI Radeon RX 590 8 GB

Re: Publicizing MacPorts [installation]

[Artem Loenko via macports-dev]

Yes, thanks for the tips! I am pretty sure that it is possible to automate it 
one way or another. But my point is that it would be helpful to have a 
one-liner to install MacPorts and maintain it as a part of the main repository.

Regards,
Artem

> On 22 May 2021, at 15:01, Bjarne D Mathiesen  wrote:
> 
> 
> 
> Joshua Root wrote:
>> On 2021-5-22 23:17 , Bjarne D Mathiesen wrote:
>>> 
>>> My own installation script looks something like this :
>>> 
>>> #!/usr/bin/env bash
>>> 
>>> prefix=$(1:-'/opt/local')
>>> version=${2:-'2.7.0'}
>> 
>> I you want to automatically use the latest version, it can be found in
>> .
>> 
>> - Josh
>> 
> 
> so something like this :
> declare version=$( curl --url
> 'https://raw.githubusercontent.com/macports/macports-base/master/config/RELEASE_URL'
> )
> version=${version##*/v}
> 
> 
> -- 
> Bjarne D Mathiesen
> Korsør ; Danmark ; Europa
> ---
> denne besked er skrevet i et totalt M$-frit miljø
> OpenCore + macOS 10.15.7 Catalina
> MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
> ATI Radeon RX 590 8 GB

Re: Publicizing MacPorts [installation]

[Bjarne D Mathiesen]

Joshua Root wrote:
> On 2021-5-22 23:17 , Bjarne D Mathiesen wrote:
>>
>> My own installation script looks something like this :
>>
>> #!/usr/bin/env bash
>>
>> prefix=$(1:-'/opt/local')
>> version=${2:-'2.7.0'}
> 
> I you want to automatically use the latest version, it can be found in
> .
> 
> - Josh
> 

so something like this :
declare version=$( curl --url
'https://raw.githubusercontent.com/macports/macports-base/master/config/RELEASE_URL'
)
version=${version##*/v}


-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
OpenCore + macOS 10.15.7 Catalina
MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
ATI Radeon RX 590 8 GB

Re: Publicizing MacPorts [installation]

[Joshua Root]

On 2021-5-22 23:17 , Bjarne D Mathiesen wrote:


My own installation script looks something like this :

#!/usr/bin/env bash

prefix=$(1:-'/opt/local')
version=${2:-'2.7.0'}


I you want to automatically use the latest version, it can be found in 
.


- Josh

Re: Publicizing MacPorts [installation]

[Bjarne D Mathiesen]

Artem Loenko via macports-dev wrote:
> INSTALLATION
> 
> The current process is described well[1], but it is almost impossible to
> automate it. For a tool that supposes to be a CLI to manage everything,
> this is a disadvantage for me. Yes, I can install MacPorts from the
> command-line with something like this in my Makefile:
> 
...

My own installation script looks something like this :

#!/usr/bin/env bash

prefix=$(1:-'/opt/local')
version=${2:-'2.7.0'}

if [ ! -e MacPorts-${version}.tar.gz ]
then
curl -L -O --url
"https://github.com/macports/macports-base/releases/download/v${version}/MacPorts-${version}.tar.gz;
fi

rm  -rf  ./MacPorts-${version}
tar -zxf   MacPorts-${version}.tar.gz 2>/dev/null \
|| { echo "error expanding MacPorts-${version}.tar.gz" ; exit }

cd MacPorts-${version}
CC=/usr/bin/cc ./configure \
 --prefix=/opt/local \
 --with-install-user=root \
 --with-install-group=admin \
 --with-directory-mode=0755 \
 --enable-readline \
&& make SELFUPDATING=1 \
&& make install SELFUPDATING=1 \
|| { echo "error compiling MacPorts-${version}" ; exit }

# update MacPorts itself
${prefix}/bin/port -dN selfupdate

# let's get bash, zsh & nano
${prefix}/bin/port -N install bash  && echo "${prefix}/bin/bash" >>
/etc/shells
${prefix}/bin/port -N install zsh   && echo "${prefix}/bin/zsh"  >>
/etc/shells
${prefix}/bin/port -N install nano

# cleanup
cd ..
rm  -rf  ./MacPorts-${version}

(this is actuallly part of a bigger script system I (desperately) try to
maintain at https://trac.macports.org/wiki/howto/AdvancedDailyAdm )

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
OpenCore + macOS 10.15.7 Catalina
MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
ATI Radeon RX 590 8 GB

Re: Publicizing MacPorts [bundles]

[Bjarne D Mathiesen]

Artem Loenko via macports-dev wrote:
> BUNDLES
> 
> Homebrew supports bundles[3] where you can list all the software you use
> and install it with a simple `brew bundle` command. It is a convenient
> way to track a list of software you use, migrate between machines or set
> up remote hardware on CI/CD. With MacPorts, I found only one way to do
> so – Makefile or a shell script where I list all the packages I need.
> Not a big deal, you can say, and it is true. But one of the reasons to
> use Homebrew over MacPorts.

I've got a problem w/ bundles : they -almost- never install -or- do what
I need 樂

Lets take something like the LAMP stack:
L : it's a given (macOS)
A : apache24 ; ngix
M : MySQL ; Percona ; MariaDB ; Postgresql ; sqlite
P : php72, php73, php74, php80 ; python ; perl

and for php in particular : which extensions are needed ?
as to the different php-versions : I had to play around w/ Magento &
Typo3. At that time, I had php73 installed ; BUT they had only certifed
themselves up to php72 and simply refused to install under php73, so I
had to || install php72 and modify my Apache24 conf ; & presently
WordPress doesn't recommend php80; & one of the modules WordPress really
recommends (php80-imagick) isn't available yet for php80, but can be
installed from source [thread: Re: [errors] php80-imagick ; 21/01/2021]

So : bundles is a nice idea; but I regard them as for the intermediate
user - not the advanced.

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
OpenCore + macOS 10.15.7 Catalina
MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
ATI Radeon RX 590 8 GB

Re: Publicizing MacPorts

[Artem Loenko via macports-dev]

Hello there,

I agree with all the points about publicity (blog posts, Twitter, etc.). But I 
want to share the opinion on MacPorts from a (power?) user who is aware of the 
tool and “deep in my heart” believe that MacPorts is a better option than, for 
example, Homebrew.

INSTALLATION

The current process is described well[1], but it is almost impossible to 
automate it. For a tool that supposes to be a CLI to manage everything, this is 
a disadvantage for me. Yes, I can install MacPorts from the command-line with 
something like this in my Makefile:

```
macports: ## Install/Upgrade MacPorts
ifeq (, $(shell which port))
$(eval TEMP_PKG := $(shell mktemp -t macports).pkg)
curl --silent --output $(TEMP_PKG) --remote-name 
https://distfiles.macports.org/MacPorts/MacPorts-2.6.4_1-11-BigSur.pkg 

sudo installer -pkg $(TEMP_PKG) -target /
rm -Rf $(TEMP_PKG)
```

But then I have to maintain the URL, update it if I do not want to migrate, etc.
You can compare it with the Homebrew approach[2]:

```
/bin/bash -c "$(curl -fsSL 
https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh 
)”
```

It may sound like a minor issue. But simplicity and efficiency are important, I 
believe. From my point of view, it is easy to improve it:
1. Have a symlink to the latest available version (e.g. 
https://distfiles.macports.org/latest-macos-11.pkg 
)
2. Have a script that will detect the macOS version on the machine (`sw_vers 
-productVersion` or something) and download the proper package
3. Run the installer with `installer -pkg …`

GUI APPLICATIONS

This is a controversial topic. As you know, you can install and manage GUI 
macOS applications with so-called Homebrew `casks`[4]. From the user 
perspective, there are no differences between CLI and GUI applications, and I 
just want to manage applications I use with ONE package manager. In the case of 
MacPorts, I cannot install even open-source applications (like Firefox, 
NetNewsWire, etc.). 
Yes, I understand that someone has to maintain such ports. But if we are 
talking about publicity, new users and experience, it is vital to have at least 
the most popular software on the list.

BUNDLES

Homebrew supports bundles[3] where you can list all the software you use and 
install it with a simple `brew bundle` command. It is a convenient way to track 
a list of software you use, migrate between machines or set up remote hardware 
on CI/CD. With MacPorts, I found only one way to do so – Makefile or a shell 
script where I list all the packages I need. Not a big deal, you can say, and 
it is true. But one of the reasons to use Homebrew over MacPorts.

CONCLUSIONS

Why I like MacPorts but use Homebrew? Because it is a convenient way to manage 
your packages seamlessly (starting from the installation process and to the 
point of how you maintain the list of software you use).
And again, from my point of view, publicity could (and should) help, but the 
user experience is an important aspect as well. For now, even the statement 
from the main page – Install and upgrade open-source software on macOS – is not 
entirely true, unfortunately.

P.S. Do not get me wrong. You do a great job maintaining the tool for many 
years; thank you for this! And there are cases when I prefer MacPorts over 
other solutions. Please, consider this message as my attempt to help and 
contribute to the discussion.


[1] https://www.macports.org/install.php 
[2] https://brew.sh/ 
[3] https://github.com/Homebrew/homebrew-bundle 

[4] https://github.com/Homebrew/homebrew-cask 


Regards,
Artem