Re: Using the PEAR Installer for non-PEAR projects

Markus Fischer wrote: > > Hi, > > I'm just throwing in a bunch of ideas I had. It may some are > already covered or planned to do be done. If so, just point > me in the right direction, thx ;) Stig will for sure enhance my reply. That's all about I can say: > .) Installer defaults to PEAR_INSTALL_DIR but can be > configured to install to anywhere the user wants it to (e.g. > ~/.pearrc or by command line switch) # Temporary package relocation $ pear -d php_dir=<some dir> install Package.tgz # Permanent relocation # -s Store the conf for that user $ pear -d php_dir=<some dir> -s # -S Store the conf for the whole system $ pear -d php_dir=<some dir> -S $ pear install Package.tgz > .) Installer can handle multiple repositories (remote, local, > wherever, much like debians /etc/apt/sources.list) Right now can handle _different_ repositories not multiple. > .) Installed not only detects dependencies but can download > them automatically (even never version of a package). Even > when sebastion writes: > > pear install http://www.sourceforge.net/.../release.tar.gz > > and this release needs SOAP, this dependencies is detected > and if a repository is configured it is tried to download and > install it from there. It's planned to work so, at least for PEAR packages in the near future. Not only that, in the wish list, it will be able to handle packages composed by many packages (a tar with a special multi-package definition file). > OTOH, the package.xml in the release.tar.gz may contain an > URI where to find a package this release dependens on. This > could be just another > http://www.anotherhost/.../other-package-release.tar.gz . This is for you Stig :-) > Depending on the users preference such dependencies are > automatically resolved (i.e. donwload and install without > prompt) or may be prompted to do so) > > .) Interactive shell (CPAN?) > I personally hate interactivity, specially the CPAN one. Questions needs answers, answers needs knowledge. Tomas V.V.Cox