<div dir="ltr">Greg,<br><br>I'd suggest putting it in a subcollection named examples, so it at least gets installed _somewhere_. Users can always write (require <collection>/examples/<whatever>) and use the online syntax checker to jump to the file, if it's otherwise hard to find. If compiling the examples is burdensome, you can add them to compile-omit-paths in info.rkt so they don't have to be compiled at installation time for your package.<br>
</div><div class="gmail_extra"><br clear="all"><div>Carl Eastlund</div>
<br><br><div class="gmail_quote">On Fri, Apr 5, 2013 at 2:46 PM, Greg Hendershott <span dir="ltr"><<a href="mailto:greghendershott@gmail.com" target="_blank">greghendershott@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On reflection, 3 seems impossible, since the content of the package is<br>
whatever is in the Git repo. In other words, the .pkgignore that I<br>
want _is_ .gitignore.<br>
<br>
Anyway, if anyone has any suggestion whether I should prefer 1 or 2,<br>
please let me know. Thanks.<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, Apr 5, 2013 at 2:38 PM, Greg Hendershott<br>
<<a href="mailto:greghendershott@gmail.com">greghendershott@gmail.com</a>> wrote:<br>
> I just made rackjure and markdown into packages for Not-Named-Planet-2. ;)<br>
><br>
> This was easy to do! It went well (unless someone informs me it did<br>
> not go well).<br>
><br>
> Next, I want to make frog into a package.<br>
><br>
> Currently it's:<br>
><br>
> frog/<br>
> <source files><br>
> example/ # an example site -- purely example, not a unit test<br>
><br>
> I understand I need to shift it down to:<br>
><br>
> frog/<br>
> frog/<br>
> <source files><br>
><br>
> My question is what to do about example/ ?<br>
><br>
> 1. If it put it under frog/frog with the source, then it will be part<br>
> of the `frog` collection. Unfortunately it will be buried in some<br>
> collections folder the user might not know to examine (as was the case<br>
> with Planet 1). So it's sort of hidden deadweight.<br>
><br>
> 2. If I leave `example` at the top, under frog/ then it would seem<br>
> like a "collection" named `example`. Trying to raco setup it won't<br>
> cause an error, but, that doesn't seem right.<br>
><br>
> 3. Maybe the best choice is to ignore it, in the sense of .gitignore.<br>
> Users could still refer to it on GitHub, but it wouldn't be installed<br>
> at all via raco pkg install.<br>
><br>
> But, is 3 even possible -- is there a ".pkgignore" equivalent of .gitignore?<br>
____________________<br>
Racket Users list:<br>
<a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br>
<br>
</div></div></blockquote></div><br></div>