On Mon, Jul 28, 2003 at 02:01:23PM +0200, Andreas Raab wrote:
> As far as I am aware Monticello doesn't support both. You can either ship
> the .mcv, violating point a) or you can do an export, violating point b).
> Please, *PLEASE* tell me that I'm wrong.
> 
I think you are wrong: If you do a .st fileout of a monticello
package, people can install it very simple by filing it in.

And if they would like to have it back as a monticello package,
they would simple define a new one (e.g. "Balloon3D"). Because
the Balloon FileIn was allready done with monticello, it's
garanteed that the conventions regarding PackageInfo are
correct (System-Cathegories Balloon3D* and all extensions
to other classes are in *balloon method-categories), so
the .mcv will be the same as yours, but without branching info.

The only thing you'd loose would be the actual versioning
information about where this particular version is supposed
to be in the history of the original Balloon3D repository,
but that may be not that important in this case, because
if even if someone makes a change and mails you the mcv, you
can use the Diff-feature of Monticello to see the differences
and import them in your version... So for integration of changes
into a project where the code is under the guidane of a single
person, shipping .mcv shouldn't be that important...

(All this off course only in I understand monticello correctly)

    Marcus 


-- 
Marcus Denker marcus at ira.uka.de  -- Squeak! http://squeak.de