Re: more bundle identification possibilities

> packagename-version#bundle // original idea > packagename-version?bundle // also URL-like > packagename-bundle-version // various bundle second punctuation ideas > packagename.bundle-version // java-like > packagename/bundle-version // filesystem-like > packagename+bundle-version // additive? > packagename[bundle]-version // mimic php array access > packagename(bundle)-version // mimic function call > bundle@packagename-version // email-like > channel://packagename-version.bundle > channel://packagename-version?bundle > channel://packagename-version/bundle > channel://packagename-version#bundle > channel://user:pass@packagename-version.bundle > channel://packagename-version.tgz?bundle Greg, After reading all the recent mails on bundles and subpackages, I am confused. Could you explain the difference between the bundles and subpackages, and the relationship between bundles and packages? If I think of bundles, I picture something like say, Auth + The complete set of dependancies, or something else fun like say, Mail_IMAP + Net_IMAP, or maybe even PEAR::Text_Wiki + CIAWEB::YAWP (Hi Paul!). To me, right now, Bundles sound like a quick way to define a set of packages that don't depend on each other, but can work together nicely. As such, cross-channel connections would be nice to have, me thinks. Cipri