<div dir="ltr">Updating from the lastest alpha image, which is how we'll produce release image, will never get ToolBuilderTests.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 12, 2013 at 1:18 PM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ah, but that unloading was manual?<br>
<span class="HOEnZb"><font color="#888888"><br>
frank<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 12 December 2013 19:16, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
> I have ToolBuilder-Tests after updating from trunk. I unloaded<br>
> ToolBuilderTests.<br>
><br>
><br>
> On Thu, Dec 12, 2013 at 12:37 PM, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Despite the lack of a ToolBuilderTests, and the presence of a<br>
>> ToolBuilder-Tests package, Monticello Browser tells me that I have a<br>
>> ToolBuilderTests, not a ToolBuilder-Tests.<br>
>><br>
>> frank<br>
>><br>
>> On 11 December 2013 20:56, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
>> > OK, I think I've done the right thing - mind giving it a check?<br>
>> ><br>
>> > frank<br>
>> ><br>
>> > On 11 December 2013 11:20, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>><br>
>> > wrote:<br>
>> >> Thanks, Chris. I've prepped the changes, and I'll push them tonight.<br>
>> >><br>
>> >> frank<br>
>> >><br>
>> >> On 11 December 2013 02:19, Chris Muller <<a href="mailto:ma.chris.m@gmail.com">ma.chris.m@gmail.com</a>> wrote:<br>
>> >>> - delete ToolBuilderTests-fbs.2 too, since you have its code in the<br>
>> >>> new -1.<br>
>> >>><br>
>> >>> On Tue, Dec 10, 2013 at 8:17 PM, Chris Muller <<a href="mailto:ma.chris.m@gmail.com">ma.chris.m@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>>> Since there is no ancestry yet, you can remove the ancestry and start<br>
>> >>>> over:<br>
>> >>>><br>
>> >>>> - Delete working copy ToolBuilderTests.<br>
>> >>>> - Add ToolBuilderTests back (+Package button). Ancestry is now<br>
>> >>>> clean.<br>
>> >>>> - Use the rename function from the menu to rename ToolBuilderTests to<br>
>> >>>> ToolBuilder-Tests.<br>
>> >>>> - Save ToolBuilder-Tests-fbs.1.<br>
>> >>>> - delete ToolBuilderTests-fbs.1 from the repository.<br>
>> >>>><br>
>> >>>> On Tue, Dec 10, 2013 at 2:10 PM, Frank Shearar<br>
>> >>>> <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
>> >>>>> n 10 December 2013 00:21, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
>> >>>>>>>> PS -- Since it was for aesthetic reasons, it would be better and<br>
>> >>>>>>>> more<br>
>> >>>>>>>> consistent if it were named "ToolBuilder-Tests" instead of<br>
>> >>>>>>>> "ToolBuilderTests".<br>
>> >>>>>>><br>
>> >>>>>>> Sure, but then Monticello forces you to have as many packages as<br>
>> >>>>>>> there are<br>
>> >>>>>>> ToolBuilder-Foo thingies, right? That's ok for ToolBuilder, but<br>
>> >>>>>>> for Tools<br>
>> >>>>>><br>
>> >>>>>> I was talking about ToolBuilder-*, not Tools. The other packages<br>
>> >>>>>> in<br>
>> >>>>>> the family are<br>
>> >>>>>><br>
>> >>>>>> ToolBuilder-Morphic<br>
>> >>>>>> ToolBuilder-MVC<br>
>> >>>>>> ToolBuilder-SUnit<br>
>> >>>>>><br>
>> >>>>>> Whoa! ALL of which have no definitions! Frank is this something<br>
>> >>>>>> you<br>
>> >>>>>> modularized out? So we should somehow remove these WorkingCopy's<br>
>> >>>>>> from<br>
>> >>>>>> the trunk image. Via some postscript perhaps?<br>
>> >>>>><br>
>> >>>>> Nah, I just did the wrong thing. Worse, I even paused to think about<br>
>> >>>>> the package name before doing the wrong thing. The question is: how<br>
>> >>>>> to<br>
>> >>>>> rename the package? It's trivial to rename the package through the<br>
>> >>>>> UI.<br>
>> >>>>> But now I have a ToolBuilderTests-fbs.2. Is the right thing to do<br>
>> >>>>> the<br>
>> >>>>> following?:<br>
>> >>>>> * rename the mcz to ToolBuilder-Tests-fbs.2<br>
>> >>>>> * copy that to trunk<br>
>> >>>>> * change the config map to reference this instead of<br>
>> >>>>> ToolBuilderTests-fbs.1<br>
>> >>>>><br>
>> >>>>> frank<br>
>><br>
><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>