PEAR2 & Pyrus - The look ahead
•
6 recomendaciones•2,190 vistas
- The document discusses PEAR2 and Pyrus, which are overhauls of the PEAR library and installer for PHP. - Key aspects of PEAR2 include using PHP 5.3+, a new installer, packages going through a sandbox process before release, improved documentation, and namespaces. - Pyrus is the new installer, which is easier to use, can package entire apps, and has improved security compared to the old installer. - Details are provided on how to generate PEAR2 packages and use the Pyrus installer command line.
Recomendados
Más contenido relacionado
Similar a PEAR2 & Pyrus - The look ahead
Similar a PEAR2 & Pyrus - The look ahead (20)
Más de Helgi Þormar Þorbjörnsson
Más de Helgi Þormar Þorbjörnsson (17)
Último
Último (20)
PEAR2 & Pyrus - The look ahead
- 1. PEAR2 & Pyrus, The Look Ahead
- 2. Head of R&D at echolibre , pear extraordinaire, author and from Iceland Head of R&D at echolibre , pear extraordinaire, published author and an Icelander Who is Helgi ? Head of R&D at echolibre , pear extraordinaire, author and from Iceland
- 5. Standards
- 6. Community
- 8. Mirrors
- 9. More QA (Test coverage, Doc coverage)
- 10. Documentation
- 12. High bus factor
- 14. Image issues
- 15. PEAR2 Dissected
- 17. PHP 5.3+
- 18. New Installer
- 20. Channel for stable packages only
- 21. Sandbox to main channel at beta
- 23. 50%+ code coverage in unit tests
- 24. API approved by other developers
- 28. Still Docbook
- 29. Easy to setup
- 30. Integration of full books possible (TDG)
- 31. Documentation with PhD The PEAR manual is built in 5 minutes, not hours !
- 35. Users given the choice
- 37. allfiles.php – Includes everything
- 38. Include files that are highly tweaked
- 40. Extracted packages can be upgraded
- 42. Namespaces Namespace PEAR2; class MyClass {} Namespace PEAR2TTP; class Request {} Class: PEAR2TTPequest Package Name: PEAR2_HTTP_Request
- 46. No installation of the installer just grab phar
- 47. Capable of packaging entire apps in phars
- 48. Can manage multiple installed PEAR trees
- 50. Easy packaging when using PEAR2 svn layout
- 51. More security
- 53. Faster
- 54. More robust
- 55. Better handling of PECL
- 56. Easy to embed in your app
- 58. Finishing touches on pear2.php.net
- 59. Almost ready for alpha!
- 62. php pyrus.phar [directory] command
- 64. make
- 65. package
- 66. generate-ext
- 67. pickle
- 68. build
- 70. Package info goes into README
- 71. Developer info goes into CREDITS
- 72. Release notes go into RELEASE-0.1.0
- 73. Run a 20 line package.php
- 74. Voila ! Package is created
- 76. No dependencies except for pyrus
- 77. Builds static XML and package files
- 78. No web frontend
- 79. Questions? Email: [email_address] Twitter: @h http://joind.in/talk/view/955
Notas del editor
- Sandbox available to all
- The default exception is good enough Exception implement an interface, each package has their own base exception namespace PEAR2PackageName; interface Exception {}
- Uses OpenSSL2 PKCS#12 and X.509 certificates for package signing and verification
- Smaller / Faster: Uses internal PHP 5.3+ feature to drop code size Robus: Uses XML and Sqlite3 for redundant register, can recover corrupt registries and so on
- • Build process is easier then PEAR1, no more editing XML files • Code layout has to follow the PEAR2 rules • Project info goes in Readme file • Developer list goes in Credits file • Release notes go in Release-0.1.0 file • Run makepackage.php • Get a package