bundles

From: Date: Sat, 11 Sep 2004 22:09:50 +0000
Subject: bundles
Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-33348@lists.php.net to get a copy of this message
Hi, I'm finding things working along quite nicely with channels, and in the process of revamping the PEAR_Downloader class so I can read the darn thing, I've designed a method similar to parseDSN() from DB that parses a package name. Currently, this is the format we have: [channelname::]packagename[-version|-state][.tar|.tgz] This works nicely, as in pear::DB-1.6.5 pear::Cache-stable.tgz DB PEAR-alpha etc. When bundles are introduced, they will be collections of packages that are installed together, similar to the way --alldeps or --onlyreqdeps works. The difference is that bundles can also contain unrelated packages (such as a bundle of PFC classes) that share no dependencies but the author has found people want to install them all together. Bundles can also specify a subset of optional dependencies, to install, for instance, a particular set of packages needed to process a peculiar database-oriented function. The particulars aside, how about using a format similar to html anchors for bundles? [channelname::]packagename[-version|-state][.tar|.tgz][#bundlename] pear::PEAR-1.4.0dev12.tgz#developer This command, for instance, would install the PEAR package with the developer bundle. The developer bundle would include all of the packages needed to do proper creation and management of a PEAR package. My main question, however, is not about the content of bundles, but about how to refer to them on the command-line. I would like to use an --option, but this fails if you install multiple packages at once $ pear install PEAR#developer DB#mysql this hypothetical would install the developer package for PEAR, and only the mysql drivers for DB. A similar syntax could also be used at uninstall-time $ pear uninstall DB#full to avoid the hypothetical $ pear uninstall DB DB_mysql DB_mssql DB_oracle Greg

« previous php.pear.dev (#33348) next »