{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia6b4hdkyyjdtruvgtlo24gztuxsetlhauxd2ftcrz3hcjwezzt74",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkltxqfudte2"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=3#post_41",
  "publishedAt": "2026-04-28T23:05:33.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I'm aware of `[lib.name]`, and as you note it's confusing to users. For example, this is permitted in the current implementation:\n\n\n    [package]\n    name = \"fa47a84c-a7a9-4cc2-bdd4-e8aedf4f96b0\"\n\n    [lib]\n    name = \"xml\"\n\n\nAnd such a package could be depended on like this:\n\n\n    [dependencies]\n    xml = { package = \"fa47a84c-a7a9-4cc2-bdd4-e8aedf4f96b0\", version = \"1.0.15\" }\n\n\nI've considered doing that, but it feels kinda slightly hostile, so I wanted to see if there was some other way to be able to publish my packages without completely going against current best practices.",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}