[squeak-dev] Package name prefix-matching (was: modularity goals (was: The Trunk: ToolBuilderTests-fbs.1.mcz))

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Tue Dec 10 22:39:37 UTC 2013


In extreme situation, we can overwrite a mcm update map...


2013/12/10 Frank Shearar <frank.shearar at gmail.com>

> On 10 December 2013 22:30, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> > That won't help.  There are two files "version" & "package" in the mcz
> that know what the package is really called.  If you write a tool to
> rewrite those u may get lucky but easier is to rename in the Monticello
> browser or write a script to do the same in the image.
>
> I did that. Right click, rename package, then save. That results in a
> ToolBuilderTests-fbs.2 with the correct changes (as in the system
> categories have been changed). But I suspect that having a package
> "ToolBuilder-Tests" in mczs named "ToolBuilderTests" will wreak havoc
> with developers and tools alike.
>
> One option is to roll back time, and
> * revert to the pre-split ToolBuilder-Kernel,
> * delete the ToolBuilderTests mczs from trunk,
> * resplit with the correct name,
> * adjust the config
>
> Except. Except that Levente issued a new config map, so we have at
> least two config maps containing "ToolBuilderTests", so deleting mczs
> is a really bad idea.
>
> frank
>
> frank
>
> > Eliot (phone)
> >
> > On Dec 10, 2013, at 12:10 PM, Frank Shearar <frank.shearar at gmail.com>
> wrote:
> >
> >> n 10 December 2013 00:21, Chris Muller <asqueaker at gmail.com> wrote:
> >>>>> PS -- Since it was for aesthetic reasons, it would be better and more
> >>>>> consistent if it were named "ToolBuilder-Tests" instead of
> >>>>> "ToolBuilderTests".
> >>>>
> >>>> Sure, but then Monticello forces you to have as many packages as
> there are
> >>>> ToolBuilder-Foo thingies, right?  That's ok for ToolBuilder, but for
> Tools
> >>>
> >>> I was talking about ToolBuilder-*, not Tools.  The other packages in
> >>> the family are
> >>>
> >>>  ToolBuilder-Morphic
> >>>  ToolBuilder-MVC
> >>>  ToolBuilder-SUnit
> >>>
> >>> Whoa!  ALL of which have no definitions!  Frank is this something you
> >>> modularized out?  So we should somehow remove these WorkingCopy's from
> >>> the trunk image.  Via some postscript perhaps?
> >>
> >> Nah, I just did the wrong thing. Worse, I even paused to think about
> >> the package name before doing the wrong thing. The question is: how to
> >> rename the package? It's trivial to rename the package through the UI.
> >> But now I have a ToolBuilderTests-fbs.2. Is the right thing to do the
> >> following?:
> >> * rename the mcz to ToolBuilder-Tests-fbs.2
> >> * copy that to trunk
> >> * change the config map to reference this instead of
> ToolBuilderTests-fbs.1
> >>
> >> frank
> >>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131210/92ba92d7/attachment.htm


More information about the Squeak-dev mailing list