…st, let's not run the require call - this allows for more sensible autoloading in certain environments (i.e. non-PEAR installs)
… of a phar archive is necessary. This is best suited for use with automated processes, to prevent the unnecessary distribution of archives that are rebuilt if a change is made, but the source files aren't affected. When phar archives are rebuilt, it seems that their file contents change slightly and will register as an altered file, even though the source files held within haven't changed (e.g. doc files being updated in a package, or another library changes...latest git commit id changes, but the source files are the same). This can save a decent amount of bandwidth, processing, and time - if used correctly this will ensure that phar archive rebuilds do not occur until it is actually necessary.
… within the build process
…5.3 possibly, reported by chevrox)