[racket-dev] Hacking on the collects

I develop in the same git clone that I use. If I change collect X, I test
after running "raco setup X" and once I'm satisfied. I run "raco setup" to
see if other things were affected. I then run tests on things other than X
that I know depend on it. Then I push.

If you do a pull request on github, it will not be useful because github is
a mirror and I'll just need to get the patch some other way anyways. I'd
rather you sent the patch directly to me. [Because the websockets stuff is
code I maintain.]

Jay

On Mon, Dec 6, 2010 at 10:04 AM, Jakub Piotr Cłapa <jpc-ml at zenburn.net>wrote:

> I added support for secure websockets to net/websocket/client and now I am
> wondering how I should make such changes in th future to easily integrate
> them back into racket?
>
> What I have tried:
> 1. Fork racket on github
> 2. Make a local copy
> 3. Compile everything fro scratch
> 4. Wait and awful lot of time
> 4. Change the file in collects
> 5. Run make install
> 6. Wait another awful lot of time for raco setup to recomplie everything
> 7. Test the changes
> 8. I was planning to create a pull request on github
>
> Is there a easier/faster way? Or should I just develop in the "live"
> collects tree and then endure the "raco setup" once for final testing?
>
> Thanks for any suggestions.
>
> --
> regards,
> Jakub Piotr Cłapa
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev




-- 
Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay

"The glory of God is Intelligence" - D&C 93
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20101206/1b6dc5d7/attachment.html>