@rejeep We cannot do it that way.  I tried, but it doesn't work.

The handler created by that function always uses the full path of the given URL, so if we start the handler for the packages directory, it will try to read files from `packages/packages/…`.

What we could to, however, is to get rid of the `packages/` URL prefix generally.  package.el should work just fine, if servant serves the packages and the archive index directly from the root URL.  And if we intend to make servant reusable as pluggable handler for elnode, we should not use a hardcoded prefix anyway.