<div dir="ltr">Looks great to me.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 3, 2013 at 7:36 AM, Matthew Flatt <span dir="ltr"><<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I went to fix a typo (`tech' to `racket') and ended up moving and<br>
tweaking the text. I hope the changes are ok.<br>
<br>
I like the way the example distinguishes the package name, collection<br>
name, and library name, and so I added a sentence to explicitly note<br>
that `require' lines don't refer to packages. Then again, it also<br>
seemed worth nothing that a package will often supply a collection<br>
whose name matches the package.<br>
<div class="HOEnZb"><div class="h5"><br>
At Wed, 2 Jan 2013 14:03:45 -0700, Jay McCarthy wrote:<br>
> Sounds fine. John's original language seems like that and is good to me.<br>
><br>
><br>
> On Wed, Jan 2, 2013 at 1:59 PM, Carl Eastlund <<a href="mailto:cce@ccs.neu.edu">cce@ccs.neu.edu</a>> wrote:<br>
><br>
> > It doesn't need to be phrased as a comparison to Planet1, but it can be<br>
> > given as a reassurance that this "package system" thingy does not add any<br>
> > baggage to require lines.<br>
> ><br>
> > Carl Eastlund<br>
> ><br>
> ><br>
> > On Wed, Jan 2, 2013 at 3:49 PM, Jay McCarthy <<a href="mailto:jay.mccarthy@gmail.com">jay.mccarthy@gmail.com</a>>wrote:<br>
> ><br>
> >> I agree in that context that it is useful as a part of the "What's<br>
> >> different about Planet 2?" And it's there (question 6).<br>
> >><br>
> >> But, in the context of a new Racket user learning about packages, I don't<br>
> >> see a reason to add the baggage of how it's different than some system<br>
> >> they've never used.<br>
> >><br>
> >> Jay<br>
> >><br>
> >><br>
> >> On Wed, Jan 2, 2013 at 1:40 PM, Carl Eastlund <<a href="mailto:cce@ccs.neu.edu">cce@ccs.neu.edu</a>> wrote:<br>
> >><br>
> >>> There _is_ reason to think these modules are different, because they<br>
> >>> were different in Planet1. I've had to remind myself several times that<br>
> >>> Planet2 packages don't have special require forms, and that's just during<br>
> >>> discussions -- I haven't even been writing code with them yet. Clarifying<br>
> >>> that Planet2 simplifies the require lines, and makes user packages on a<br>
> >>> peer level with built-in collections, is a useful thing to put early on in<br>
> >>> the Planet2 docs.<br>
> >>><br>
> >>> Carl Eastlund<br>
> >>><br>
> >>><br>
> >>> On Wed, Jan 2, 2013 at 3:27 PM, Jay McCarthy <<a href="mailto:jay.mccarthy@gmail.com">jay.mccarthy@gmail.com</a>>wrote:<br>
> >>><br>
> >>>> The documentation already says "A package is a set of modules for some<br>
> >>>> number of collections." And there's no reason to think that these modules<br>
> >>>> are different from other modules, so I don't see why we need to point out<br>
> >>>> that they are required like all other modules are.<br>
> >>>><br>
> >>>> If you think it's very confusing, then feel free to push the commit<br>
> >>>> with two small changes:<br>
> >>>><br>
> >>>> 1. The docs don't use the term "planet2", so just say "the Racket<br>
> >>>> package manager"<br>
> >>>><br>
> >>>> 2. Consider using the same examples from the rest of the docs (such as<br>
> >>>> data/matrix from tic-tac-toe)<br>
> >>>><br>
> >>>> Jay<br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>> On Wed, Jan 2, 2013 at 12:30 PM, John Clements <<br>
> >>>> <a href="mailto:clements@brinckerhoff.org">clements@brinckerhoff.org</a>> wrote:<br>
> >>>><br>
> >>>>> As I was trying to assembly my first planet2 package, I found myself<br>
> >>>>> wondering how exactly to 'require' modules associated with planet2<br>
> >>>>> packages. My initial assumption (require them like any other collection<br>
> >>>>> containing modules) turned out to be correct, but there was a period when<br>
> I<br>
> >>>>> doubted this, and I think it should be documented.<br>
> >>>>><br>
> >>>>> Below is a proposed doc change; I'll commit it if you like it, or<br>
> >>>>> abandon it if not. I'm including the (git format-patch) text and also<br>
> >>>>> attaching it as a file.<br>
> >>>>><br>
> >>>>> John<br>
> >>>>><br>
> >>>>><br>
> >>>>><br>
> >>>>> >From d3f72c47820effb240532c518378dc9709d69600 Mon Sep 17 00:00:00 2001<br>
> >>>>> From: John Clements <<a href="mailto:clements@racket-lang.org">clements@racket-lang.org</a>><br>
> >>>>> Date: Tue, 1 Jan 2013 10:40:40 -0800<br>
> >>>>> Subject: [PATCH] added docs on requiring planet2 modules<br>
> >>>>><br>
> >>>>> ---<br>
> >>>>> collects/planet2/scribblings/planet2.scrbl | 14 ++++++++++++++<br>
> >>>>> 1 files changed, 14 insertions(+), 0 deletions(-)<br>
> >>>>><br>
> >>>>> diff --git a/collects/planet2/scribblings/planet2.scrbl<br>
> >>>>> b/collects/planet2/scribblings/planet2.scrbl<br>
> >>>>> index e9e565a..81d6e58 100644<br>
> >>>>> --- a/collects/planet2/scribblings/planet2.scrbl<br>
> >>>>> +++ b/collects/planet2/scribblings/planet2.scrbl<br>
> >>>>> @@ -200,6 +200,20 @@ imply a change in the @tech{checksum}.<br>
> >>>>><br>
> >>>>> @section{Using Packages}<br>
> >>>>><br>
> >>>>> +Modules installed using planet2 may be @tech{require}d like any other<br>
> >>>>> +modules. For instance, if the package @pkgname{recipes} contains<br>
> >>>>> +the module file @filepath{vegan/fruitsalad.rkt}, then package users<br>
> >>>>> +who have this package installed may evaluate<br>
> >>>>> +<br>
> >>>>> +@racketblock[(require vegan/fruitsalad)]<br>
> >>>>> +<br>
> >>>>> +...to require this module.<br>
> >>>>> +<br>
> >>>>> +@; ----------------------------------------<br>
> >>>>> +<br>
> >>>>> +@section{Managing Packages}<br>
> >>>>> +<br>
> >>>>> +<br>
> >>>>> The Racket package manager has two user interfaces: a command line<br>
> >>>>> @exec{raco}<br>
> >>>>> sub-command and a library. They have the exact same capabilities, as<br>
> >>>>> the command line interface invokes the library functions and<br>
> >>>>> --<br>
> >>>>> 1.7.7.5 (Apple Git-26)<br>
> >>>>><br>
> >>>>><br>
> >>>>><br>
> >>>><br>
> >>>><br>
> >>>> --<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>
> >>>> _________________________<br>
> >>>> Racket Developers list:<br>
> >>>> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
> >>>><br>
> >>>><br>
> >>><br>
> >><br>
> >><br>
> >> --<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>
> ><br>
> ><br>
><br>
><br>
> --<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 Developers list:<br>
> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
</div></div></blockquote></div><br><br clear="all"><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
</div>