Re: My first post here: a request to clarify my interpretation of the "Delegations" section of slashpackage/names.html.

Ellenor Bjornsdottir <[email protected]> wrote:
> Might such a domain owner then have a package named
> host/example.net/wugdaemon - using a slash directly after her domain,
> so as not to create example.net-wugdaemon clutter in /package/host?

As the owner of example.net, yes, you could create a package named
host/example.net/wugdaemon.  You should not create one called
host/example.net-wugdaemon, not just because of clutter, but because
that name would belong to the owner of the domain
"example.net-wugdaemon".  That domain probably won't ever actually
exist, but syntactically similar names like "example.net-x.cr.yp.to"
illustrate the problem.  The whole pathname component immediately
under host/ should be a domain name that you control.

> Furthermore, is it encouraged that the use of host/ package names be
> reported to this mailing list? Should registration be attempted for
> host/ package names?

That's not necessary, but if those packages include command names that
are intended to be unique in $PATH, then it's good to register those
names.

> Does the owner of example.net also control
> host/subdomains-of.example.net?

Yes, assuming the owner hasn't delegated control of such a name to
someone else who might publish their own packages.