On Sat, Dec 8, 2012 at 9:27 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">30 minutes ago, Jay McCarthy wrote:<br>
</div><div class="im">> On Sat, Dec 8, 2012 at 8:29 PM, Eli Barzilay <<a href="mailto:eli@barzilay.org">eli@barzilay.org</a>> wrote:<br>
><br>
> > One other thing that I think is important in a migration path is<br>
> > keeping any modification made to the source of the packages that are<br>
> > already installed.<br>
><br>
> 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.<br>
><br>
> They are in the same place. However, I thought the whole premise of<br>
> this proposed behavior is that the package won't work in the new<br>
> version of Racket, so certainly the package system can't be<br>
> responsible for doing a merge your local changes and whatever the<br>
> updated version of the package needs.<br>
<br>
</div>I'm not following that -- the compiled files and the sources are in<br>
the same place? If so then it makes the whole migration thing kind of<br>
impossible with local changes, no? (And I wasn't thinking about<br>
merging, just reusing the same sources.)</blockquote><div><br></div><div>:) Now I'm not following you.</div><div><br></div><div>If you have a package named P that has a module A/B/C.rkt then on your disk is in:</div>
<div><br></div><div>~/.racket/$version/pkgs/P/A/B/C.rkt</div><div><br></div><div>with its compiled code in: </div></div><div><br></div><div><div>~/.racket/$version/pkgs/P/A/B/compiled/C_rkt.zo</div><div><br></div><div>My idea of "raco pkg migrate" is just to get a list of the packages that you have installed and re-install them. I think if we assume that Racket versions will break package P then those same problems will prevent you from keeping local changes; especially if the package system isn't responsible for running merge, which it clearly shouldn't be. (Now, I don't think that's a reasonable assumption, i.e. I think version-less should be the default, but I've clearly been out-voted.)</div>
<div><br></div><div>Jay</div><div><br></div></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>