Re: proposal: pear install-deps command

Hi, The only thing that will need to be implemented is a check for optional dependencies in this code, and prompting for the user (perhaps with a javascript popup in the web frontend, and just normal prompting in the command-line). I'm delighted to hear you have code to do this already :) Greg "Tomas V.V.Cox" <cox@idecnet.com> wrote in message news:002201c32d61$e85f8e80$0d0a0a0a@COX... > I wrote long time ago the experimental code for adding the pear command a > real dependecy database (located at Registry.php from line 512). I will > allow to detect recursive dependencies, detect dependecy breaks on > uninstall, things like: > > # pear install pack1 pack3(needed_for_pack2) pack2(needed_for_pack1) > > # pear uninstall pack2(needed_for_pack1) > Error: pack1 depends on pack2 > > # pear install --follow-deps pack1 > Downloading/Installing pack3(needed_for_pack2) > Downloading/Installing pack2(needed_for_pack1) > Downloading/Installing pack1 > > I'll retake that work in the next days (AFAIR the code was working good, > just needed deep tests). The good news is that the dependecies db could be > built from scratch at any time, even over an already installed system. > > Tomas V.V.Cox > > ----- Original Message ----- > From: "Greg Beaver" <greg@chiaraquartet.net> > To: <pear-dev@lists.php.net> > Sent: Sunday, June 08, 2003 1:28 AM > Subject: [PEAR-DEV] proposal: pear install-deps command > > > > Hi, > > > > I would like to propose a new command, install-deps. This command would > > work > > exactly like pear install, except that it would automatically > > install/upgrade > > required packages specified in the <deps> section. It should also prompt > to > > install/upgrade optional dependencies. > > > > I will be happy to implement this command when I return in July, if no one > > else is interested/has time. > > > > This would have obvious benefits for applications like phpDocumentor, as > > applications by definition rely on multiple packages. It would allow the > > reduction of size for a PEAR install by a factor of quite a lot (2.4 MB is > > rather large). It would allow the splitting of phpDocumentor into a core > > package, and several Converter sub-packages, each of which depends on > > phpDOcumentor. This way, a user looking for a PDF documentation generator > > could pear install-deps PhpDocumentor_PDF and it would automatically > install > > the core of phpDocumentor. > > > > This will also simplify the Lite API proposal. phpDocumentor could depend > > on > > phpDocumentor-lite. > > > > Regards, > > Greg > > -- > > phpDocumentor > > http://www.phpdoc.org > > > > > > > > -- > > PEAR Development Mailing List (http://pear.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > >