<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hey Max,<div class=""><br class=""></div><div class="">The Zinc-Seaside package is indeed moved to the Seaside project a while back: <a href="https://github.com/SeasideSt/Seaside/issues/1050" class="">https://github.com/SeasideSt/Seaside/issues/1050</a></div><div class=""><br class=""></div><div class="">Do you have a sequence I can try to see what the problem still is?</div><div class=""><br class=""></div><div class="">Renaming it is a good idea anyway.</div><div class=""><br class=""></div><div class="">Cheers</div><div class="">Johan<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 7 May 2020, at 09:07, Max Leske <<a href="mailto:maxleske@gmail.com" class="">maxleske@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi everyone,<br class=""><br class="">I want to propose that we clean up the current situation with the Zinc-Seaside package. While it may not be much of a problem when we run tests or talk about the default setup it becomes a real problem when your baseline loads both Seaside3 and ZincHTTPComponents.<br class=""><br class="">The problem partly lies with Metacello (I already talked to Dale about it), which calculates the packages to load for a project by also including all loaded packages from that project, even when that package is not part of the<br class="">loading instruction for the project. That means, when I load Seaside3, which loads Zinc-Seaside, and then ZincHTTPComponents, Zinc-Seaside will be loaded again from ZincHTTPComponents because Zinc-Seaside already exists in the image.<br class=""><br class="">There's no way to solve this issue in the baseline (not even with fake dependency chains). From my point of view we, therefore, have two options:<br class="">- rename Zinc-Seaside in the Seaside3 image to Seaside-Zinc. That would be good because it matches the Seaside prefix (I think we should do this anyway). This would also make it possible for the Zinc-Seaside package to remain in the Zinc project if we decide we want that.<br class="">- delete Zinc-Seaside from the Zinc project (I think we should do this too), to avoid confusion.<br class=""><br class="">I talked to Sven two or three weeks ago and he thought that "ownership" of Zinc-Seaside currently resided with the Seaside project. So the question is, is there any reason to keep Zinc-Seaside in the Zinc project?<br class=""><br class=""><br class="">Please let me know what you think. I'll be happy to provide the pull requests to both projects.<br class=""><br class=""><br class="">Cheers,<br class="">Max_______________________________________________<br class="">seaside-dev mailing list<br class=""><a href="mailto:seaside-dev@lists.squeakfoundation.org" class="">seaside-dev@lists.squeakfoundation.org</a><br class="">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev<br class=""></div></div></blockquote></div><br class=""></div></body></html>