<div dir="ltr">If I am a consumer of packages do I need to make any changes to use the new system?<div><br></div><div style>For example, I have code that has:</div><div style><br></div><div style><div>(require (planet dherman/memoize:3:1))</div> <div>(require (planet jaymccarthy/dijkstra:1:2))</div><div><br></div><div style>What do I do to "point" at planet2?</div><div style><br></div><div style>Thanks,</div><div style>-joe</div></div></div><div class="gmail_extra"> <br><br><div class="gmail_quote">On Thu, Apr 4, 2013 at 8:18 AM, Jay McCarthy <span dir="ltr"><<a href="mailto:jay.mccarthy@gmail.com" target="_blank">jay.mccarthy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> In general, the new package system is designed for developers to only<br> interact with the PNR a single time, to create the package, and never<br> again. This is why it leverages git/etc so that their normal processes<br> are "just right".<br> <br> Since creating an incompatible change creates a "new" package, I think<br> it is justified in this model for them to return to the PNR. And, I<br> like the idea that they don't need to "plan ahead" in any way for this<br> sort of thing vis-a-vis their development infrastructure.<br> <span class="HOEnZb"><font color="#888888"><br> Jay<br> </font></span><div class="HOEnZb"><div class="h5"><br> On Thu, Apr 4, 2013 at 9:15 AM, Laurent <<a href="mailto:laurent.orseau@gmail.com">laurent.orseau@gmail.com</a>> wrote:<br> ><br> ><br> >><br> >> > But I see that many packages on Planet2 are using the master as the<br> >> > package<br> >> > source. Then how do the developers manage major versions and<br> >> > development?<br> >><br> >> I believe that most of these developers do not intend to ever break<br> >> compatibility. But if they do, they can tag the last "Version 1"<br> >> commit, change the PNR to point to the tag, then create a new "Version<br> >> 2" package that uses "master". The PNR source record can be changed<br> >> whenever you want and it is not cached, etc by users, so when you<br> >> change it, they will get the update just like usual.<br> ><br> ><br> > Ah wonderful, that answers my concerns.<br> ><br> > Thank you very much for your answers.<br> ><br> > Laurent<br> ><br> <br> <br> <br> </div></div><div class="HOEnZb"><div class="h5">--<br> Jay McCarthy <<a href="mailto:jay@cs.byu.edu">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> ____________________<br> Racket Users list:<br> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> </div></div></blockquote></div><br></div>