Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112322
Return-Path: <sebastian@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 57057 invoked from network); 30 Nov 2020 16:32:27 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 30 Nov 2020 16:32:27 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id E2321180538
	for <internals@lists.php.net>; Mon, 30 Nov 2020 07:59:38 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: *
X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_50,SPF_HELO_NONE,
	SPF_NEUTRAL autolearn=no autolearn_force=no version=3.4.2
X-Spam-Virus: No
X-Envelope-From: <sebastian@php.net>
Received: from scarlet.netpirates.net (scarlet.netpirates.net [188.94.27.5])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Mon, 30 Nov 2020 07:59:38 -0800 (PST)
Received: from p5de2cc90.dip0.t-ipconnect.de ([93.226.204.144] helo=[192.168.178.42])
	by scarlet.netpirates.net with esmtpsa  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94)
	(envelope-from <sebastian@php.net>)
	id 1kjlaS-0003Ks-HT
	for internals@lists.php.net; Mon, 30 Nov 2020 16:59:36 +0100
To: internals@lists.php.net
References: <CAF+90c885XVcPa6Uc3n0sAu7yhf=BSpprHRBrLcz5OC2XjCJRA@mail.gmail.com>
Message-ID: <1f12d34e-a462-8ee0-81b6-438d1702fe64@php.net>
Date: Mon, 30 Nov 2020 16:59:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c885XVcPa6Uc3n0sAu7yhf=BSpprHRBrLcz5OC2XjCJRA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] phar command
From: sebastian@php.net (Sebastian Bergmann)

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.