I use bundles, but I'm not sure you could say I *use* bundles. More
like, I abuse them. I often have a top level bundle which acts as a
configuration map - then there may be bundles underneath that to act as
a grouping mechanism for my packages.
For the top level, versioning that information is essential. However,
actually having in my image gets in the way often.. it has properties on
it that I have to manually maintain, such as prerequisites.. and if I
want to parcel it out, all heck breaks loose. If I need to change it
because it's unloadable, I have to fallback to some pretty crude tools.
Once I've got my top level bundle loaded, it serves to group things
together at the top of the RB, but beyond that it's dead-weight, another
tree click I have to perform.
For the second level, versioning and merging that information is a
burden. It's also not multifaceted, which is what I really want.. for
example, I have packages which I'd classify as: seaside, component,
contributed, to do that right now, I group said packages together in to
a bundle called SeasideImportedComponents. This is pretty suboptimal
when I want to reorganize things.
Michael
Bruce Badger wrote:
> On his Blog, Jim asked about Store Bundles:
>
> * Do you use bundles?
> * If so, how do you use them, and why?
> * If setting explicit pre-reqs was easier, would you still use bundles?
>
> I do use bundles.
>
> I use nested bundles with an outer master bundle for every project.
>
> Even if setting preq versions were easier I probably still use
> bundles. I like the explicit containment.
>
>
_______________________________________________
vwnc mailing list
vwnc@...
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
