Uploaded byHelgi Þormar Þorbjörnsson
PEAR2 & Pyrus - The look ahead
- 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.
More Related Content
Similar to PEAR2 & Pyrus - The look ahead
PEAR2 & Pyrus - The look ahead
- 1. PEAR2 & Pyrus,The Look Ahead
- 2. Head of R&Dat 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
- 3. What is PEARtoday Structured library
- 4.
- 5.
- 6.
- 7. PEAR - Newthings PEAR Group elected by developers
- 8.
- 9. More QA (Testcoverage, Doc coverage)
- 10.
- 11. PEAR - ProblemsDocumentation
- 12.
- 13.
- 14.
- 15.
- 16. What is PEAR2Concept overhaul of PEAR
- 17.
- 18.
- 19. New proposal processNew packages go into the Sandbox
- 20. Channel for stablepackages only
- 21. Sandbox to mainchannel at beta
- 22. From sandbox toproduction Complete-sih documentation
- 23. 50%+ code coveragein unit tests
- 24. API approved byother developers
- 25.
- 26.
- 27. Documentation with PhDUses the new awesome PhD
- 28.
- 29.
- 30. Integration of fullbooks possible (TDG)
- 31. Documentation with PhDThe PEAR manual is built in 5 minutes, not hours !
- 32. Exceptions No baseexception to extend from
- 33.
- 34. Include / RequireOnce Not allowed !
- 35. Users given thechoice
- 36. Include / RequireOnce PEAR2 Autoload
- 37. allfiles.php – Includeseverything
- 38. Include files thatare highly tweaked
- 39. Unzip and goClassical unzip just works
- 40. Extracted packages canbe upgraded
- 41. Namespaces Will beused in PEAR2
- 42. Namespaces Namespace PEAR2;class MyClass {} Namespace PEAR2\HTTP; class Request {} Class: PEAR2\HTTP\Request Package Name: PEAR2_HTTP_Request
- 43.
- 44.
- 45. The new installerEasier to use
- 46. No installation ofthe installer just grab phar
- 47. Capable of packagingentire apps in phars
- 48. Can manage multipleinstalled PEAR trees
- 49. The new installerCustom tree can use deps from the system
- 50. Easy packaging whenusing PEAR2 svn layout
- 51.
- 52. The new installerSmaller
- 53.
- 54.
- 55.
- 56. Easy to embedin your app
- 57. Status Waiting forPHP 5.3.1
- 58. Finishing touches onpear2.php.net
- 59. Almost ready foralpha!
- 60.
- 61. How to usephp pyrus.phar command
- 62. php pyrus.phar [directory]command
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69. Handling package xmlfiles Use the standard directory structure
- 70. Package info goesinto README
- 71. Developer info goesinto CREDITS
- 72. Release notes gointo RELEASE-0.1.0
- 73. Run a 20line package.php
- 74. Voila ! Packageis created
- 75. Simple Channel ServerPEAR Channel info REST server
- 76. No dependencies exceptfor pyrus
- 77. Builds static XMLand package files
- 78.
- 79. Questions? Email: [email_address] Twitter: @h http://joind.in/talk/view/955
Editor's Notes
- #9 Sandbox available to all
- #14 The default exception is good enough Exception implement an interface, each package has their own base exception namespace PEAR2PackageName; interface Exception {}
- #23 Uses OpenSSL2 PKCS#12 and X.509 certificates for package signing and verification
- #24 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
- #28 • 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