[packaging] Package for doctest

[Boris Kolpackov]

Markus Pawellek <markuspawellek at gmail.com> writes:

> But I would appreciate suggestions for improvements because I am
> unexperienced concerning the packaging process.

I took a quick browse and overall it looks very sensible. A couple
of minor nitpicks:

1. You can probably remove repositories.manifest -- it's highly
   unlikely this package will have any dependencies.

2. I see the description-file in the manifest points to
   README_PACKAGE.md. Generally, for cases like this, we would
   probably want to point it to upstream/README.md since we
   display this information in the repository web interface,
   for example:

   https://cppget.org/libstud-uuid
   
   Maybe try it and see what happens ;-)?


> If you would like to put this package into the build2 packaging
> account, what would be the best procedure for me to publish it?

I've invited you to the build2-packaging organization so you should
be able to move it there. Probably makes sense to call the repository
just doctest rather than build2-doctest, similar to other packages.

Once you've done this, it would be great if you could also publish
it to cppget.org using the bdep-publish command. This section in the
introduction has the details:

https://build2.org/build2-toolchain/doc/build2-toolchain-intro.xhtml#guide-versioning-releasing

Thanks!