PIE installable with Composer?

[asgrim]

Split from: #98 (comment)

Should PIE be installable with Composer?

$ composer global require php/pie

Points to note:

• currently php/pie is the namespace; I believe this is a protected namespace on Packagist, so I would need to discuss with Packagist team about submitting this
• in theory, this allows people to composer require php/pie (per project) which doesn't make any sense to do

Currently the only supported distribution mechanism is downloading the PHAR from the https://github.com/php/pie/releases page. Other distribution mechanisms should be carefully evaluated on a case-by-case basis.

[alexandre-daubois]

I think it would be really nice. This way, if one day Pie allows to read from composer.json and install extensions listed in the file, we could even imagine having a postscript that then triggers Pie and install extensions after the packages. Just thinking out loud.

It would be so convenient to arrive on a project, and do compose install && vendor/bin/pie install ... because Composer installer Pie.

this allows people to composer require php/pie (per project) which doesn't make any sense to do

On the different projects I worked on, it's quite often that devs doesn't install Composer globally. I can understand that, some people like to have their projects a bit siloed without having to install tools globally on their system. In my opinion, having the choice is a good thing.

[macintoshplus]

IMO pie must be executed before the composer because the composer checks if all extension is installed.

[jnoordsij]

+1 for this; especially on local environments I can see the benefits of this, as then composer global update php/pie is an easy way to update pie which complies to any constraint you have setup in your global composer.json file.

IMO pie must be executed before the composer because the composer checks if all extension is installed.

Theoretically with this, you could do the following oneliner (untested) to first install pie through composer (local project), then run it to install all required extensions and then finally ensure they are all present:

composer install --ignore-platform-reqs && vendor/bin/pie install ... && composer check-platform-reqs

Also: adding dev to the flags in composer.json should ensure that users are presented with a warning on running composer require php/pie (see https://getcomposer.org/doc/04-schema.md#keywords), with composer require php/pie --dev making some sense for the above usecase.

[Bellangelo]

If we make Pie installable by composer it would make sense to make Pie independent to any PHP extension. Otherwise, you could get into a paradox where you would like to install PIe for an extension but composer does not let you because Pie needs this extension as well.

So, I would suggest to try and replace any extensions using polyfills. I could help on this.

Running composer check-platform-reqs gives currently these results:

composer-plugin-api  2.3.0     success                                       
composer-runtime-api 2.2.2     success                                       
ext-ctype            *         success provided by symfony/polyfill-ctype    
ext-dom              20031129  success                                       
ext-filter           8.2.23    success                                       
ext-json             8.2.23    success                                       
ext-libxml           8.2.23    success                                       
ext-mbstring         *         success provided by symfony/polyfill-mbstring 
ext-openssl          8.2.23    success                                       
ext-pcre             8.2.23    success                                       
ext-phar             8.2.23    success                                       
ext-reflection       8.2.23    success                                       
ext-simplexml        8.2.23    success                                       
ext-spl              8.2.23    success                                       
ext-tokenizer        8.2.23    success                                       
ext-xml              8.2.23    success                                       
ext-xmlwriter        8.2.23    success 

[asgrim]

I don't think any polyfills are needed. You should exclude dev dependencies; and it also helps to understand why certain extensions are needed, e.g.:

$ composer check-platform-reqs --no-dev
Checking non-dev platform requirements for packages in the vendor dir
ext-ctype   *        success provided by symfony/polyfill-ctype 
ext-openssl 8.3.15   success                                    
ext-pcre    8.3.15   success                                    
php         8.3.15   success                            

$ composer why ext-ctype 
Package "ext-ctype *" found in version "8.3.15".
vimeo/psalm      5.26.1 requires ext-ctype (*) 
webmozart/assert 1.11.0 requires ext-ctype (*) 

$ composer why ext-openssl
Package "ext-openssl *" found in version "8.3.15".
composer/ca-bundle 1.5.4 requires ext-openssl (*) 

$ composer why ext-pcre
Package "ext-pcre *" found in version "8.3.15".
composer/ca-bundle     1.5.4  requires ext-pcre (*) 
netresearch/jsonmapper v4.5.0 requires ext-pcre (*) 

pcre is a core extension anyway, and ctype and openssl are bundled extensions, which are typically included in distributions anyway. I have kept external dependencies to a minimum for exactly this reason anyway.