as I lay --cloning

[Matthew Butterick]

I want to incorporate some `raco pkg update --clone ...` commands into my Racket build script. But a couple, like `drracket` and `scribble`, pop a prompt as shown below, which interrupts the build to ask for manual intervention. Is there a command-line option that would automatically clone everything, equivalent to typing "a" at the prompt? (similar to how `raco pkg install --auto` suppresses prompts to install dependencies)


Querying Git references for drracket at git://github.com/racket/drracket/?path=drracket
Updating:
drracket
packages from a Git repository would not share a local clone
repository: git://github.com/racket/drracket/
local clone: /Users/mb/git/drracket/
packages for local clone:
drracket
non-clone packages:
drracket-tool-lib
drracket-tool-doc
drracket-plugin-lib
Convert the non-clone packages to clones, too? [Y/n/a/c/?]

[Sam Tobin-Hochstadt]

I think you want `--multi-clone convert`.

Sam

> --
> You received this message because you are subscribed to the Google Groups "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/B89010DC-8286-4172-A5A3-DB752EBA9AE3%40mbtype.com.
> For more options, visit https://groups.google.com/d/optout.

[Robby Findler]

FWIW, I've been pretty happy running that command only once and having
it persist.

Robby

[Matthew Butterick]

On Dec 12, 2016, at 9:20 AM, Robby Findler <ro...@eecs.northwestern.edu> wrote:

FWIW, I've been pretty happy running that command only once and having
it persist.

Perhaps I'm doing it wrong: 

When I rebuild from source I first detonate my copy of the `racket` repo and reset on HEAD so that I know that the build is totally clean & fresh.

But that also detonates my installation-wide packages (and clones).

Is there a middle ground?

[Robby Findler]

I just don't blow so much away. "git pull --ff-only" and "make" at the
top-level seems to be pretty robust.

Robby