Re: [racket] input requested on tools for Racket library developers

2012-01-04 Thread Grant Rettke
On Mon, Jan 2, 2012 at 11:10 PM, Neil Van Dyke wrote: > If you develop Racket libraries, or would like to, this is a request for > input... Something like Apache Maven's effective-pom http://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html that shows you all of the dependenci

Re: [racket] input requested on tools for Racket library developers

2012-01-03 Thread Matthias Felleisen
disseminate for all three architectures? On Jan 4, 2012, at 2:14 AM, Noel Welsh wrote: > Sounds like you're making a build tool, which is great! The basic > commands I want, in addition to what you've mentioned are: > > init -- Initialise an empty project with default files and directory stru

Re: [racket] input requested on tools for Racket library developers

2012-01-03 Thread Noel Welsh
Sounds like you're making a build tool, which is great! The basic commands I want, in addition to what you've mentioned are: init -- Initialise an empty project with default files and directory structure test -- Run my tests If you're writing a build tool, there should probably be some Makefile e

Re: [racket] input requested on tools for Racket library developers

2012-01-03 Thread Doug Williams
I guess the only additional thing I can think of is to also tie McFly into the bug tracker. What I am thinking is to also have the issue resolution embedded in the source files. Is there a preview of the embedded documentation available for us to look at and comment on now. [Forgive me if it has be

[racket] input requested on tools for Racket library developers

2012-01-02 Thread Neil Van Dyke
If you develop Racket libraries, or would like to, this is a request for input... I want to make it easier for myself and others to develop reusable Racket libraries that wind up in PLaneT in a timely manner. The initial problem was to make it easier to do documentation, by embedded it in th