I didn't respond to this thread originally because I believe that Racket is generally "anti-stubbing". The concept of a "racket project" basically doesn't exist, because everything is supposed to be "inside" the language. For instance, if you want to create a module with tests, then you just create a file named m.rkt and put in
#lang racket/base (module+ test (require rackunit)) and you're done. There's nothing more that you would want to do. You can write documentation inline too, but admittedly you have to create a info.rkt and at least one scrbl file. As far as the "boring stuff" of creating a package... the package system is designed so that that is just "mkdir pkg-name". You don't need to do anything else. Even if you want to distribute the package, you just need to make sure the directory is online somewhere. As you get more sophisticated as a developer you could do "git init", but it's supposed to be incremental and a low barrier. Jay On Sat, Dec 14, 2013 at 1:36 AM, Laurent <[email protected]> wrote: > On Fri, Dec 13, 2013 at 11:14 PM, Ryan Davis <[email protected]> wrote: >> >> I'd also be perfectly happy with `raco new <projectname>` w/ a boilerplate >> project w/ a module, tests, and doco stubbed out. >> >> Is there anything in the package ecosystem like this? > > > Not that I know of, but it's a good idea. It would probably look more like > `raco pkg new` (or `raco pkg init`). > A `raco pkg git-new` and a `raco pkg github-new` that do all the boring > stuff for you may also be quite convenient, if such things are possible. > > Laurent > > > ____________________ > Racket Users list: > http://lists.racket-lang.org/users > -- Jay McCarthy <[email protected]> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 ____________________ Racket Users list: http://lists.racket-lang.org/users
