So I just renamed rackjure's manual.scrbl to rackjure.scrbl. On the next raco setup I get:
raco setup: --- building documentation --- raco setup: WARNING: duplicate tag: (def ((lib "rackjure/alist.rkt") alist)) raco setup: in: <unknown> raco setup: in: /Users/greg/src/scheme/collects/rackjure/rackjure/rackjure.scrbl raco setup: WARNING: duplicate tag: (def ((lib "rackjure/alist.rkt") current-curly-dict)) raco setup: in: <unknown> raco setup: in: /Users/greg/src/scheme/collects/rackjure/rackjure/rackjure.scrbl ... and many more... The message about <unknown> is confusing. But anyway, I assume this is because the new rackjure.scrbl output is conflicting with the old manual.scrbl output. OK, so I should probably remove rackjure, then retry raco setup. However: raco pkg remove rackjure raco pkg remove: cannot remove packages that are dependencies of other packages dependencies: rackjure (required by: (markdown toml frog)) I could remove those and try again...but. Now I'm a little concerned how this will play out in the field for users of rackjure. Renaming the file is easy for me. But will it trigger a cascade of re-installs that succeed (best-case, or do not succeed, worst case)? _________________________ Racket Developers list: http://lists.racket-lang.org/dev
