undoing (or redoing) --clone?

['John Clements' via dev-redirect]

I cloned a pkg in the wrong directory. How can I fix this? I would simply remove and re-install, but the package in question is htdp-lib, and many packages depend on it. I tried

raco pkg update —clone <new-dir> pkg

… which told me that it was already cloned, and

raco pkg update pkg

… which just updated the thing where it was.

Am I missing something obvious? I usually am. Thanks in advance!

John

[Matthew Flatt]

Use

raco pkg update --lookup <pkg>

to revert to un-cloned mode, and then you can try `--clone` again.

> --
> 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/51ebf0c7-2203-4a3c-a582-452487d158
> ff%40mtasv.net.
> For more options, visit https://groups.google.com/d/optout.

['John Clements' via dev-redirect]

> On Oct 23, 2015, at 2:09 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote:
>
> Use
>
> raco pkg update --lookup <pkg>
>
> to revert to un-cloned mode, and then you can try `--clone` again.

Yep, that’s right there, isn’t it. I suppose I expected it to be part of

/ --link : Link a directory package source in place (default for a directory)
| --static-link : Link in place, promising collections do not change
| --copy : Treat directory sources the same as other sources
| --clone <dir> : Clone Git and GitHub package sources to <dir> and link
| --source : Strip packages' built elements before installing; implies --copy
| --binary : Strip packages' source elements before installing; implies --copy
\ --binary-lib : Strip source & documentation before installing; implies —copy

I’ll just console myself with the thought that perhaps others will search and find this thread useful.

Thanks!

John