• Supports the embedding of documentation directly in source files, together with the McFly Runtime package.

• Maintains PLaneT development links, based on metadata in "info.rkt", information from the PLaneT server, and current activity using McFly Tools.

• Programmatically updates "info.rkt" files to add any missing definitions. (This uses the progedit package.)

• Automates building PLaneT archive files for upload to the PLaneT server.

• Creates initial "info.rkt" and "main.rkt" for a project.

(require (planet neil/mcfly-tools))

1. Put any files you already have for the package into a directory. Let’s say you ultimately want your package to be named “foo,” so you might wish to name the directory "foo". (But you don’t have to name it "foo".)

2. Go into the directory, and run the command:
     raco mcfly init
   This does the following:

   • Creates an "info.rkt" if you don’t already have one in the directory; or modifies your existing one.

   • Creates a "main.rkt" if you don’t already have one.

3. Look at "info.rkt", especially all the “;; TODO:” comments. Make any necessary changes. Perhaps most importantly for now:

   • At the very least, you’ll need to edit the value for mcfly-planet, to set it to the PLaneT owner name, and to check that the package name and version are correct. If you don’t yet have a PLaneT account, you can set the owner to a placeholder that you’re unlikely to forget to change later, like “myplanetownername” so that the definition might now look like:

     (define mcfly-planet 'myplanetownername/foo:1:0)

   • If your embedded documentation doc forms will not be in "main.rkt", then change mcfly-start to indicate which file will have them.

4. If you want to have your implementation and documentation in "main.rkt", and if raco mcfly init just created this file for you, it should contain a skeleton file to get you started. You actually should be able to do raco mcfly view now, to view formatted documentation in your Web browser.

5. If you don’t want to have your implementation and documentation in "main.rkt", but raco mcfly init just created that file for you, then, for ease of PLaneT require forms, you might wish to have a "main.rkt" anyway, that merely re-provides definitions from some other module. For example, if file "foo.rkt" has your implementation, you can edit "main.rkt" to look like:

   "main.rkt"

   #lang racket/base

   (require "foo.rkt")

   (provide (all-from-out "foo.rkt"))

   A reason you might want to do this comes from working with files from multiple packages at once: many tools, including DrRacket and Emacs, are easier to navigate when the files you’re editing are named things like "foo.rkt" and "bar.rkt", rather than "main.rkt" and "main.rkt".

1. Check that you have added the appropriate version history entry to your (doc history ...) form. (Note that McFly Tools does not currently check this, so check manually.)

2. Check "info.rkt", especially that the version number in mcfly-planet is correct for this upload.

3. Do a final raco mcfly setup and double-check that whatever tests you have still run.

4. Do:
     raco mcfly planet-archive
   Or:
     raco mcfly pa

5. Wait a minute for it to finish. If it works, it will create a staging directory, copy files according to mcfly-files into that directory, adjust PLaneT development links, run the make-planet-archive procedure, clean up the staging directory, re-adjust PLaneT development links, and leave you with a "packagename.plt" file.

6. You might want to test installation with use of raco planet fileinject and manipulating your PLaneT cache and links and such. McFly Tools doesn’t yet automate this part.

7. Finally, upload your "packagename.plt" file to the PLaneT server, double-checking the version before you click the button.