|
»
»
« Return to Thread: [vwnc] Bundles
Re: [vwnc] Bundles
by Andre Schnoor
::
Rate this Message:
Joachim,
thanks for the good instructions on how to make a bundle safe for
archiving.
My concern however is, that all the manual steps required to achieve
this are tedious and error prone. For me, fixing the properties of
140+ packages manually is a show stopper. I'm not charging my
customers based on hourly rates ;-)
I would love to see a menu item "Make Bundle Snapshot" that
accomplishes all this automatically in one go (especially setting all
prerequisite versions and publishing required base packages, if
changed). This could also be an option in the "Publish" dialog.
I still envy those who successfully manage to keep released products
along with development streams in the same repository over a long
period of time. Those many "Merge", "Compare" and "Reconcile" dialogs
and confirmaton messages always confused me and I did not yet have the
time to really understand the workflow and basic concept through
experimentation. IMO this is a steep learning curve that could be
flattened a lot, if the user interface was aggregated into a single
"Store Browser" with tabs that includes it all in one place very much
like the System Browser.
Andre
Am 16.05.2008 um 22:27 schrieb Joachim Geidel:
>> 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.
...
_______________________________________________
vwnc mailing list
vwnc@...
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
thanks for the good instructions on how to make a bundle safe for
archiving.
My concern however is, that all the manual steps required to achieve
this are tedious and error prone. For me, fixing the properties of
140+ packages manually is a show stopper. I'm not charging my
customers based on hourly rates ;-)
I would love to see a menu item "Make Bundle Snapshot" that
accomplishes all this automatically in one go (especially setting all
prerequisite versions and publishing required base packages, if
changed). This could also be an option in the "Publish" dialog.
I still envy those who successfully manage to keep released products
along with development streams in the same repository over a long
period of time. Those many "Merge", "Compare" and "Reconcile" dialogs
and confirmaton messages always confused me and I did not yet have the
time to really understand the workflow and basic concept through
experimentation. IMO this is a steep learning curve that could be
flattened a lot, if the user interface was aggregated into a single
"Store Browser" with tabs that includes it all in one place very much
like the System Browser.
Andre
Am 16.05.2008 um 22:27 schrieb Joachim Geidel:
>> 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.
...
_______________________________________________
vwnc mailing list
vwnc@...
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
« Return to Thread: [vwnc] Bundles
| Free Forum Powered by Nabble | Forum Help |
