<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 4:21 PM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">>> PS -- Since it was for aesthetic reasons, it would be better and 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 there are<br>
> ToolBuilder-Foo thingies, right? That's ok for ToolBuilder, but for Tools<br>
<br>
I was talking about ToolBuilder-*, not Tools. </blockquote><div><br></div><div>It's an example. ToolBuilder is easy cuz there's a package called ToolBuilder-Kernel. Look at Tools and you'll see the more general naming issue.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> The other packages 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 you<br>
modularized out? So we should somehow remove these WorkingCopy's from<br>
the trunk image. Via some postscript perhaps?<br>
<br>
> it doesn't fly. It forces<br>
> Tools-Deployment-Base, Tools-Deployment-Browser, Tools-Deployment-Debugger<br>
> et al so one can have Tools-Deployment & Tools-Tests. This is better<br>
> long-term (can pattern e.g. match off Foo-Deployment) but more work up-front<br>
> than moving Tools-Tests to ToolsTests.<br>
<br>
I don't know whether something changed recently but... What I<br>
remember encountering was that clicking "Browse" on, i.e., Tools in<br>
the MC browser would show me everything in the image that was prefixed<br>
with "Tools", INCLUDING "Tools-Tests".<br></blockquote><div><br></div><div>Yes. But we're talking about splitting things into packages. If you split, say. Tools-Browser into its own package you can't have Tools-Base, Tools-Debugger, et al in the same package. They *all* have to go into separate packages.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For that reason, when I decided to extract a "-Tests" package from<br>
Magma, I had to rename the original categories (which had no suffix)<br>
with a "-Core" suffix as well as the package. I developed the "rename<br>
package..." function of the MC Browser for this purpose.<br>
<br>
Now, however, browsing "Tools" gives me only those categories starting<br>
with "Tools-". So, maybe something changed.<br>
<br>
So, you're right, I would not rename ToolsTests to Tools-Tests. But<br>
nor would I choose the "Deployment" nomenclature if we decided to<br>
tackle it. Something else..<br></blockquote><div><br></div><div>Good short words much preferred. Deployment is an awful mouthful. </div></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>