<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 3, 2013 at 12:37 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">If I'm asking why a class should belong in two PackageInfos it's only<br>
fair I answer why it shouldn't: Because by the PackageInfo domain<br>
model mirroring MC's model, they are able to work together better.<br>
For example, the use-case I cited previously was one-click building<br>
.sar packages (MaSarPackage on SqueakMap). Utilities like that are<br>
much easier to build and maintain when the cardinalities between the<br>
models match.</blockquote><div><br></div><div>A class can belong to more than one Monticello package too.</div><div><br></div><div>Colin</div><div><br></div></div></div></div>