We do use bundles, and sub-bundles, and sub-sub-bundles, and in fact
pretty much all of our packages would be totally useless without the
other packages in their bundle.
One of the reasons for this is that our software runs on both VW and VA,
and we must be able to maintain synchronization between our Store and
Envy repositories. One of the things that makes this possible is that
the structure of packages and bundles in our Store repository and the
applications and subapplications in our Envy repository is exactly the
same for the fairly large subset of our code that is the same in both.
VW-specific code is separated into packages that don't have an analogue
in Envy, and VA-specific code is separated into subapplications that
don't have an analogue in Store.
So for us bundles act as configuration maps, as containers for
deployment packaging, as browsing convenience, as providers of load and
unload actions, and as a somewhat clunky method of fulfilling
prerequisites.
If you wanted us to stop using bundles you'd have to provide something
(or things) at least as good for each of these.
Regards,
-Martin
_______________________________________________
vwnc mailing list
vwnc@...
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
