Re: [vwnc] Bundles

Andre Schnoor schrieb am 13.05.2008 12:15 Uhr:
> Yes. I would rather see bundles in their "configuration map" role,  
> i.e. associate a specific set of packages (with versions) and their  
> load order for the purpose of loading products into an image and for  
> deploying them.
>
> Bundles should be safe for archiving: Loading an older product from an  
> archived configuration map for maintenance should be possible even  
> after years (maybe it already is and I missed something).

Yes, this is already possible. You have to make sure that
- you have the right version of VisualWorks, i.e. a visual.im from the
VW version which was the base for the product version, and the right
version of the VM,
- all prerequisites have been defined with the version of the prerequisite,
- all prerequisites should have the type "bundle" or "package", but not
"parcel" or "any",
- which implies that everything which you have loaded from parcels
should be published to Store and loaded from there, simply to make sure
that you don't accidentally load a parcel which has been modified or
replaced in the meantime,
- all non-Smalltalk files (images, shared libraries, configuration files
etc.) should be attached to a bundle and versioned in Store, and VW
should be configured such that it copies them from Store to the file
system when you build the product.

That should be sufficient, if I haven't forgotten something. We have
"top level bundles" for our products, and when we load them into a base
image, they load everything needed via versioned prerequisites without
manual intervention. The process is completely deterministic, and we can
reconstruct any product version which has not been explicitly deleted
from the repository.

Joachim
_______________________________________________
vwnc mailing list
vwnc@...
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc