Last night I deployed PGXN::Manager v0.2.1 and uploaded the first distribution, pair. If you follow that link you’ll see three files:

• pair-0.1.0.json is metadata file generated by PGXN manager to describe the distribution. Most of its data is taken from the META.json included in the uploaded zip file, but a few keys, like “sha1”, are generated, and others, like “release_status” are added if they’re not in the included META.json.
• pair-0.0.1.readme is a copy of the README file distributed with pair.
• pair-0.1.0.pgz is the distribution zip file. That’s the file you want to download, unzip, and build and install.

Following the spec I previously wrote up, there are a number of other files that get created when a new distribution is uploaded to PGXN. For the pair extension, we got:

• by/dist/pair.json, which will be updated with information for every release of the “pair” distribution.
• by/extension/pair.json, which will be updated for every upload containing the “pair” extension.
• by/owner/theory.json, which will be updated every time I upload a distribution.

• Files for every tag listed in the metadata are also created. In this case, that includes:

  • by/tag/key value pair.json
  • by/tag/key value.json
  • by/tag/ordered pair.json
  • by/tag/pair.json
  • by/tag/variadic function.json

  Each of these files will be updated every time a distribution is uploaded containing the relevant tag.

You’ll soon be able to upload your own extension distributions to PGXN. If you’re interested, please subscribe to the mail list, where I’ll soon be inviting folks to get an account and start uploading.

But first, a blog post on how to create a PGXN-friendly distribution archive. Coming up shortly.