Support subcollections in collection field in info.rkt

[countvajhula]

Currently, the collection field needs to be set to a top level collection or to multi. In either case, adding modules like my-lib/a/b/c and my-lib/a/b/d require creating a folder structure resembling this in the source repo:

my-lib/
  info.rkt
  a/
    b/
      c.rkt
      d.rkt

... even if these are the only modules provided by the package. That is, the source repo must introduce the entire collection path hierarchy to the directory structure of the repo even when the higher levels are empty.

It could be preferable to be able to specify a subcollection path in info.rkt, like:

(define collection "my-lib/a/b")

And then the repo could have the structure:

info.rkt
c.rkt
d.rkt

Or, as the top level is hopeless, something like:

src/
  info.rkt
  c.rkt
  d.rkt
...

Examples: Many repos introduce a tests subfolder in what is already designated as a test package containing only tests. See Megaparsack, Marionette, Pict, Qi.

[samdphillips]

This repo is for the package index, and I think the functionality you want needs to be in the pkg library which is in the
racket repo.