You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually when I wrote this post (2022-02-19), the current context is :
phar-io/manifest 2.0.3
phar-io/version 3.1.1
phar-io/manifest is not able to create a Manifest document with data from any OSS Composer installation.
Main reason is limitation to Semantic versioning handled by phar-io/version that did not support yet some string format accepted by Composer.
Even, if I would like in first attempt to create a PharIoManifestBuilder compatible with the manifest.xsd, I realized that my manifest builder cannot be analysed by the PharIo\Manifest\ManifestLoader with a script like example-01.php.
Second reason is the few usage by the community itself.
When we look on Packagist for dependents, there are so few projects that used it to create a manifest.xml
PHPUnit 9.5 used the phar-io/manifest package only to look for compatible PHPUnit extensions loadable by the --extensions option.
See PHPUnit\Runner\Extension\PharLoader component.
Even Phar.io that have more than 40 OSS registered that didn't use phar-io/manifest
Here is a snapshot of statistic usage on all projects registered.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Actually when I wrote this post (2022-02-19), the current context is :
phar-io/manifest
2.0.3phar-io/version
3.1.1phar-io/manifest
is not able to create a Manifest document with data from any OSS Composer installation.Main reason is limitation to Semantic versioning handled by
phar-io/version
that did not support yet some string format accepted by Composer.Even, if I would like in first attempt to create a
PharIoManifestBuilder
compatible with the manifest.xsd, I realized that my manifest builder cannot be analysed by thePharIo\Manifest\ManifestLoader
with a script like example-01.php.Second reason is the few usage by the community itself.
When we look on Packagist for dependents, there are so few projects that used it to create a
manifest.xml
PHPUnit 9.5 used the
phar-io/manifest
package only to look for compatible PHPUnit extensions loadable by the--extensions
option.See PHPUnit\Runner\Extension\PharLoader component.
Even Phar.io that have more than 40 OSS registered that didn't use
phar-io/manifest
Here is a snapshot of statistic usage on all projects registered.
Legend:
phar-io/manifest
availablephar-io/manifest
not availableThird reason to not adopt it. The
phar-io/manifest
project is not used by other to provide a manifest contents, but as a requirements checker.See Phive implementation with the
PharIo\Phive\Phar
component and thePharIo\Phive\CompatibilityService
Beta Was this translation helpful? Give feedback.
All reactions