[racket-dev] should package "X" imply package "X-test"?

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Tue Oct 15 20:40:27 EDT 2013

Actually, on second thought, I think I'm going to buck the trend here and
answer "yes" to the question in the subject line.

Two scenarios come to mind: someone hears about some cool new library and
then does something like 'raco pkg install math'. Next thing, something
goes wrong and they ask about it on a mailing list and get the response
"Run this code: (require ...)" which ends up running something from the
test suite of that library [1]. In that case, we'd probably like them to
have everything related to the library.

Second: someone decides to build a library that depends on the, say, the
math library and they have to choose what to put in their info.rkt file.
They don't want to put math no matter if it includes the tests or not,
since they don't to force their clients to install the docs. So they'll put

In other words, I don't see a lot of value in a pkg name taken up for the
lib+docs subset of some (conceptual) pile of code, but I do see value in
the "everything" pile and the "non-docs non-tests" pile. So I'd say that
the name "X" (from the subject) should mean everything.

... at least for a library. For an app, I'm less clear.


[1] this actually happened recently as you probably recall (altho
'test-floating-point' may not be in the math-test pkg)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20131015/999a5d55/attachment.html>

Posted on the dev mailing list.