we do use bundles and sub bundles
1. as a configuration maps(closed) for the release versions and
modifications for them. I can always compare them and see the
differences form version to version...or I can go back to fix an error
or create a patch to the earlier released version.
2. as a way to package different versions of the application with
different feature set, for example with or without network support.
I try to stay away from prerequisites i.e. our bundle do not have
prerequisites( or just very basic ones) - we load them into the already
pre-configured "base" images, where all of the required parcels( and/or
packages)are already loaded. Same strategy applies to the building
runtime images -I produce the parcels from my version bundle, load them
int the pre-configured base runtime image and strip... This adds one
extra step to deploy new version of VW into the development -- building
the base, but it well worth it as we know what environment we deal with
at any give time.
My 2c.
--Mark Pirogovsky
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
