Re: bundles

> [channelname::]packagename[-version|-state][.tar|.tgz] > This works nicely, as in > pear::DB-1.6.5 > pear::Cache-stable.tgz > DB > PEAR-alpha > 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 install DB#mysql A big -1 from me on this subject. The HTML anchors this is based on link to a specific part of a webpage, so in the case above, my first reaction would be that this command would install JUST the mysql driver of the DB package. A bundle as you describe it now sounds more like a collection of packages, and not as a subpackage. It'd be easier to do as for example Debian does, and make empty packages that are nothing more then an empty package with dependancies. Cipri