I'm not sure if what I'm seeing is a bug or whether I'm using the package system incorrectly, but here goes:
I just submitted a package to the package server whose source is a simple URL. It's not a Git repo accessible via HTTPS; it's a Fossil repo, with a server running that serves up a plain old tar-and-gzip'd directory. The error message from the build process: pkg: mismatched checksum on package package source: https://example.com/cool-package/tarball/trunk/download.tar.gz expected: "" got: "a5d851da2832c0b43f7530794987da0a080ebe6d" The naive way to read this error message is: OK, I need to specify a checksum. But there's no checksum field in the form on the package server. You can specify a URL and nothing else. After some digging, I found that checksums can be specified in an info.rkt file, but to my mind that shouldn't be necessary. My thinking is: if I just give a simple URL, the package server should just download the thing, make some reasonable guess about the content (in this case, it can be inferred from the media type in the server's response, but barring that, calling the `file` utility will reveal it's a gzip'd tar file, etc.), and we're off to the races. Am I thinking about things incorrectly? Are my expectations too high? What can I do? (Please don't tell me to just use Git!) Jesse -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/7ba32102-8841-45c6-a1b3-e4bffed3ae8dn%40googlegroups.com.
