Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.9.5

Request #11098 Creation of Installerless packages
Submitted: 2007-05-22 17:45 UTC Modified: 2007-10-28 01:19 UTC
From: jeichorn Assigned: cellog
Status: Closed Package: PEAR (version CVS)
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  


 [2007-05-22 17:45 UTC] jeichorn (Joshua Eichorn)
Description: ------------ Add the ability to create a tarball for a package that can be deployed without the installer. This would mean installing into a temp directory with a file layout that is self enclosed. Doing all replacements with relative paths. The ability to pull in dependencies would also be handy.

Comments

 [2007-06-01 02:42 UTC] cweiske (Christian Weiske)
This would require a shell/php script to be delivered with the package that needs to be executed.. which would be a mini-pear itself, but with deps and all it would soon be the normal pear. So what you are requesting is making pear installerless
 [2007-06-01 11:07 UTC] cellog (Greg Beaver)
actually tar xvf Package.tgz and having the package "just work" when extracted is what Josh is talking about. There are several ways that this can happen already designed into the installer and planned 1) configuration *_dir variables are stored directly in an .xml file in php_dir, so replacements are no longer necessary to access these values [already implemented] 2) baseinstalldir can be processed at packaging time rather than at installation time quite easily [packaging is not yet implemented at all] 3) package.xml will be stored in the tarball as package-[Channel]-[Package]-[version].xml so that multiple archives can be extracted into the same location without losing the package.xml information needed to be able to eventually upgrade using the PEAR installer [not yet implemented] These three factors will allow the majority of packages to "just work" on extraction. Exceptions are packages that install differently on windows and unix, and packages that need shell scripts installed into the PATH, these will require some minimal installation work. For packages with dependencies, it would just require downloading each dependency, or creating a bundle .tgz of all the deps for download-all-at-once, or even a .phar that can include all of them via require_once "BeefyPhar.phar";. The possibi
 [2007-06-01 11:07 UTC] cellog (Greg Beaver)
erm, as I was saying, the possibilities are endless :)
 [2007-06-01 11:54 UTC] jeichorn (Joshua Eichorn)
Greg described my request pretty well. The main focus on this would be for people who just don't like using an installation program.
 [2007-10-28 01:19 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. the PEAR2 standards make this possible.