TravisCI is a platform for continuous integration.
Homebrew is a package management software (that also runs on the OSX
machines that TravisCI provides).
So you can't compare both since both are totally different things.
https://en.wikipedia.org/wiki/Travis_CI
What is the pros and cons of TravisCI vs homebrew?
On 9/27/19, Tim Rühsen wrote:
> You have to clone the project via
> git clone https://gitlab.com/gnuwget/wget2.git
>
> If it helps, we have TravisCI OSX build rules in .travis_setup.sh and
> .travis.sh in the project directory. It uses homebrew
I don't find wget2 on homebrew. Can anybody make a formula for it?
On Fri, Sep 27, 2019 at 5:53 AM Tim Rühsen wrote:
> Hi Pen Yu,
>
> --compression=gzip
>
> With Wget2 these compression types are automatically use (if built in):
> gzip, deflate, bzip2, xz, lzma, br, zstd, lzip
>
> Regards, Tim
Can I understand in this way? For people who develop wget2, use
TravisCI. For people just want to use wget2, homebrew is better,
provided there is a corresponding formula.
On 9/27/19, Tim Rühsen wrote:
> Not comparable, TravisCI is a platform for continuous integration. But
> it supports OSX and
Not comparable, TravisCI is a platform for continuous integration. But
it supports OSX and we build Wget2 on it, using homebrew to install
dependencies. So anyone making up a homebrew formula might take it as
quick starter.
On 27.09.19 17:20, Peng Yu wrote:
> What is the pros and cons of TravisCI
You have to clone the project via
git clone https://gitlab.com/gnuwget/wget2.git
If it helps, we have TravisCI OSX build rules in .travis_setup.sh and
.travis.sh in the project directory. It uses homebrew to install
dependencies.
Regards, Tim
On 27.09.19 15:50, Peng Yu wrote:
> I don't find
Hi Pen Yu,
--compression=gzip
With Wget2 these compression types are automatically use (if built in):
gzip, deflate, bzip2, xz, lzma, br, zstd, lzip
Regards, Tim
On 27.09.19 05:03, Peng Yu wrote:
> Hi,
>
> curl has the option `--compressed` which will decompress the data
> automatically. But
