I'm confused about how local package development is supposed to work with `raco 
pkg install --clone`. This is turning into a deterrent to diagnosing & fixing 
bugs, and an encouragement to post issues so others can fix them.

In the dark ages, one would a) fork the main Racket repo on GitHub, b) work on 
a clone of that fork locally, and occasionally c) make pull requests, or d) 
update the fork from the upstream master. (A process well documented by Greg 
Hendershott [1])

I've read the new documentation about clone workflow. [2] And when I do this:

raco pkg install --clone typed-racket

It works as advertised. But I end up with a clone of the main typed-racket 
repo. Which is not what I want, because I'm not a core committer. Right?

So I fork it on Github to http://github.com/mbutterick/typed-racket. But when I 
try to use this fork as my <git-pkg-source>:

raco pkg install --clone typed-racket https://github.com/mbutterick/typed-racket

... it doesn't work. I get a ton of build errors. Scrutiny reveals that the 
default URL for `raco install --clone ...` looks more like this:

git://github.com/racket/typed-racket/?path=typed-racket

So I change my URL accordingly:

raco pkg install --clone typed-racket 
git://github.com/mbutterick/typed-racket/?path-typed-racket

But it still doesn't work. So either I'm overlooking something obvious in the 
syntax, or something subtle in how the model has changed.





[1] 
http://www.greghendershott.com/2013/04/a-guide-for-infrequent-contributors-to-racket.html

[2] http://www.cs.utah.edu/plt/snapshots/current/doc/pkg/git-workflow.html

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to