Le 08/12/2021 à 13:20, François Kooman a écrit :
I'm not sure how to best deal with the increased complexity of
"modern"
software, except fight it and keep things as simple as possible. It
might be unsustainable in the long run, but at least for now it more or
less works and I can deploy and test/build on EL without requiring any
packaged 3rd party PHP libraries. Not sure if this approach is something
I should pursue...
For memory, main issues for me
1/ number of packages vs number of packagers
I don't want to maintain more libraries
Already own too much without real help
2/ time waiting for package reviews
roundcubemail 1.5 was blocked for weeks because
of lack of roundcube/rtf-html-php [1]
composer 2.2 will probably be blocked because
of lack of composer/pcre [2]
3/ Exception to package review
From Review Guidelines [3]
Contributors and reviewers MUST follow the Package Review Process,
with the following exceptions:
...
* The package is being created so that multiple versions
of the same package can coexist in the distribution.
but this only apply for a "compat" package (old version)
not for a newer version, which is for now the common practice
for PHP libraries. I have tons of such packages, and I'm too
tired to submit them to review (and see §1) and don't want
having to change our common practice.
4/ Symfony
This is the most commonly used set of libraries,
but also the one for which we are unable to run tests.
Version 5 is released for a while, 6 is coming,
but we still only have 4.
Some updates are already blocked by Symfony 5
(laminas/cli, laminas/cache, php-cs-fixer...)
5/ Phar
is the new way to distribute CLI application
perhaps simple to use them in RPM
(single file in /usr/bin)
=> phpnuit, composer, phpcompatinfo, php-cs-fixer...
Remi
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=2015452
[2]
https://bugzilla.redhat.com/show_bug.cgi?id=2030376
[3]
https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuideline...