Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112325
MIME-Version: 1.0
References: <CAF+90c885XVcPa6Uc3n0sAu7yhf=BSpprHRBrLcz5OC2XjCJRA@mail.gmail.com>
In-Reply-To: <CAF+90c885XVcPa6Uc3n0sAu7yhf=BSpprHRBrLcz5OC2XjCJRA@mail.gmail.com>
Reply-To: bishop@php.net
Date: Mon, 30 Nov 2020 21:15:52 -0500
Message-ID: <CAEYWF=51FKhCcp+gxi53Cn5Z5U_PNthOX0x3nB2B6DzPCD11fw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e2f15305b55db6a9"
Subject: Re: [PHP-DEV] phar command
From: bishop@php.net (Bishop Bettini)

--000000000000e2f15305b55db6a9
Content-Type: text/plain; charset="UTF-8"

On Mon, Nov 30, 2020 at 10:56 AM Nikita Popov <nikita.ppv@gmail.com> wrote:

>
> The PHP build system currently produces a "phar" command. See
> http://manpages.ubuntu.com/manpages/xenial/en/man1/phar7.0.1.html for a
> man
> page.
>
> Apart from changes to keep it working, the last time its implementation was
> touched was back in ... 2008. I'm wondering if anyone is using this
> command?
>
> My understanding is that packaging libraries as phars is not exactly
> straightforward, and people use different tooling to achieve that.
>

I also regularly use it for inspecting phar. However, I had thought - at
some point when time allows - it'd be nice to migrate it from php-src/ to
its own phar-tools/ repository. Doing so focuses php-src/ to just the
gritty Phar implementation and lets us develop independently consumable
tooling.

--000000000000e2f15305b55db6a9--