Otherwise this package's implementation would be using the planet
package -- and causing users of this package to download the planet
package -- which doesn't seem right.
Furthermore, my understanding is that it's preferable within a package
to use a relative require -- like (require "main.rkt") -- instead of
requiring the collection itself -- like either of (require describe)
or (require (planet williams/describe/describe)). So even if this were
still a planet package, I think this would be a good change to make.
Otherwise this package's implementation would be using the planet
package -- and causing users of this package to download the planet
package -- which doesn't seem right.
Furthermore, my understanding is that it's preferable within a package
to use a relative require -- like `(require "main.rkt")` -- instead of
requiring the collection itself -- like either of `(require describe)`
or `(require (planet williams/describe/describe))`. So even if this were
still a planet package, I think this would be a good change to make.
raco setup: in <pkgs>/describe/describe
/home/racket/build-pkgs/user/.racket/6.1/pkgs/describe/describe/describe-test.rkt:20:9: require: PLaneT could not download the package "williams/describe": tcp-connect: connection failed
detail: host not found
address: planet.racket-lang.org
port number: 80
step: 1
system error: Name or service not known; errno=-2
in: (planet williams/describe/describe)
The failure is apparently just some random TCP error, but the "PLaneT" part caught my eye... wait, what.
You're welcome. BTW how I noticed this was from the "fails" message for `describe` on http://pkgs.racket-lang.org/#
```
raco setup: in <pkgs>/describe/describe
/home/racket/build-pkgs/user/.racket/6.1/pkgs/describe/describe/describe-test.rkt:20:9: require: PLaneT could not download the package "williams/describe": tcp-connect: connection failed
detail: host not found
address: planet.racket-lang.org
port number: 80
step: 1
system error: Name or service not known; errno=-2
in: (planet williams/describe/describe)
```
The failure is apparently just some random TCP error, but the "PLaneT" part caught my eye... wait, what.
Otherwise this package's implementation would be using the planet
package -- and causing users of this package to download the planet
package -- which doesn't seem right.
Furthermore, my understanding is that it's preferable within a package
to use a relative require -- like
(require "main.rkt")-- instead ofrequiring the collection itself -- like either of
(require describe)or
(require (planet williams/describe/describe)). So even if this werestill a planet package, I think this would be a good change to make.
Good catch. I overlooked that. Thanks.
You're welcome. BTW how I noticed this was from the "fails" message for
describeon http://pkgs.racket-lang.org/#The failure is apparently just some random TCP error, but the "PLaneT" part caught my eye... wait, what.
f84024e944.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.