On Sat, Dec 8, 2012 at 8:29 PM, Eli Barzilay <span dir="ltr"><<a href="mailto:eli@barzilay.org" target="_blank">eli@barzilay.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">> One other thing that I think is important in a migration path is<br></div><div class="im"> > keeping any modification made to the source of the packages that are<br> > already installed.<br> <br> </div>Yeah -- and IIUC, the difference between the two installations is<br> where the packages get installed is where the compiled files are, so<br> the sources are the same. At least I *hope* that that's how it is,<br> otherwise it's back to the whole planet "cache" things, which IMO was<br> a major mistake.</blockquote><div> </div><div>They are in the same place. However, I thought the whole premise of this proposed behavior is that the package won't work in the new version of Racket, so certainly the package system can't be responsible for doing a merge your local changes and whatever the updated version of the package needs.</div> <div><br></div><div>Jay</div></div><div><br></div>-- <br>Jay McCarthy <<a href="mailto:jay@cs.byu.edu" target="_blank">jay@cs.byu.edu</a>><br>Assistant Professor / Brigham Young University<br><a href="http://faculty.cs.byu.edu/~jay" target="_blank">http://faculty.cs.byu.edu/~jay</a><br> <br>"The glory of God is Intelligence" - D&C 93<br> </div>