<div dir="ltr">I agree in that context that it is useful as a part of the "What's different about Planet 2?" And it's there (question 6).<div><br></div><div style>But, in the context of a new Racket user learning about packages, I don't see a reason to add the baggage of how it's different than some system they've never used.</div> <div style><br></div><div style>Jay</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 2, 2013 at 1:40 PM, Carl Eastlund <span dir="ltr"><<a href="mailto:cce@ccs.neu.edu" target="_blank">cce@ccs.neu.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">There _is_ reason to think these modules are different, because they were different in Planet1. I've had to remind myself several times that Planet2 packages don't have special require forms, and that's just during discussions -- I haven't even been writing code with them yet. Clarifying that Planet2 simplifies the require lines, and makes user packages on a peer level with built-in collections, is a useful thing to put early on in the Planet2 docs.<br> </div><div class="gmail_extra"><br clear="all"><div>Carl Eastlund</div> <br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jan 2, 2013 at 3:27 PM, Jay McCarthy <span dir="ltr"><<a href="mailto:jay.mccarthy@gmail.com" target="_blank">jay.mccarthy@gmail.com</a>></span> wrote:<br> </div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"> <div dir="ltr">The documentation already says "A package is a set of modules for some number of collections." And there's no reason to think that these modules are different from other modules, so I don't see why we need to point out that they are required like all other modules are.<div> <br></div><div>If you think it's very confusing, then feel free to push the commit with two small changes:</div><div><br></div><div>1. The docs don't use the term "planet2", so just say "the Racket package manager"</div> <div><br></div><div>2. Consider using the same examples from the rest of the docs (such as data/matrix from tic-tac-toe)</div><div><br></div><div>Jay</div><div><br></div></div><div class="gmail_extra"><div><div> <br><br><div class="gmail_quote">On Wed, Jan 2, 2013 at 12:30 PM, John Clements <span dir="ltr"><<a href="mailto:clements@brinckerhoff.org" target="_blank">clements@brinckerhoff.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> As I was trying to assembly my first planet2 package, I found myself wondering how exactly to 'require' modules associated with planet2 packages. My initial assumption (require them like any other collection containing modules) turned out to be correct, but there was a period when I 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 abandon it if not. I'm including the (git format-patch) text and also 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" target="_blank">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 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 @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> <span><font color="#888888">--<br> 1.7.7.5 (Apple Git-26)<br> <br> <br> </font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <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 </font></span></div> <br></div></div>_________________________<br> Racket Developers list:<br> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br> <br></blockquote></div><br></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>