Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112324
MIME-Version: 1.0
References: <CAF+90c885XVcPa6Uc3n0sAu7yhf=BSpprHRBrLcz5OC2XjCJRA@mail.gmail.com>
 <1f12d34e-a462-8ee0-81b6-438d1702fe64@php.net>
In-Reply-To: <1f12d34e-a462-8ee0-81b6-438d1702fe64@php.net>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Mon, 30 Nov 2020 12:07:05 -0700
Message-ID: <CAAKU0unGitHZbAFOmpD67dOLousKBAXx=gFHtpq_HiQuoQWg8w@mail.gmail.com>
To: Sebastian Bergmann <sebastian@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e87fb005b557b716"
Subject: Re: [PHP-DEV] phar command
From: internals@lists.php.net ("Levi Morrison via internals")

--000000000000e87fb005b557b716
Content-Type: text/plain; charset="UTF-8"

On Mon, Nov 30, 2020 at 8:59 AM Sebastian Bergmann <sebastian@php.net>
wrote:

> Am 30.11.2020 um 16:55 schrieb Nikita Popov:
> > My understanding is that packaging libraries as phars is not exactly
> > straightforward, and people use different tooling to achieve that.
>
> While I do not use this "phar" command to package my software as PHARs, I
> use it every once in a while to look inside a PHAR. Don't know whether
> that justifies keeping it around, though.


I've used it occasionally, and almost entirely to poke around a phar (`phar
tree phpunit-9.phar`, for instance).

--000000000000e87fb005b557b716--