<div dir="ltr">So, after step 1, you also need to hunt down the various extensions - in FileStream and other places - that is part of the Compression package, and move them to one of the new packages. Otherwise you innadvertantly remove those methods. (Currently all of these are just under *Compression - no sub-category...)<div>
<br></div><div style>-Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 16, 2013 at 2:39 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"><div class="HOEnZb"><div class="h5">On 16 July 2013 22:30, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
> I would like to split the Compression package into its two constituent<br>
> subpackages, Compression-Archives and Compression-Streams.<br>
><br>
> Files depends on things in Compression-Archives, and<br>
> Compression-Streams depends on Files. If I can split the package and<br>
> replace it with the two subpackages, I can untangle this cyclic<br>
> dependency.<br>
><br>
> But how would I actually do this? I've tried making two packages, for<br>
> instance. However, the classes still remain in Compression... as you<br>
> can see if you try to unload the old Compression package.<br>
<br>
</div></div>One possible way goes something like this:<br>
* Add CompressionArchives and CompressionStream packages corresponding<br>
to the hyphenated system categories<br>
* Push a new config map with the "new" packages<br>
* Push the empty Compression package<br>
* Remove the Compression package using a config map<br>
* Rename CompressionArchives to Compression-Archives and same for Stream<br>
* Push a third config map removing Compression and adding<br>
Compression-Archives and Compression-Stream<br>
<br>
> frank<br>
<br>
</blockquote></div><br></div>