Re: Migration of pgBackRest internal support tools to Rust.
Re: Migration of pgBackRest internal support tools to Rust.
On 7/15/26 09:44, David Steele wrote: > > My proposal is to provide the files that are currently generated at > build time (html documentation, man pages, help.auto.c.inc, > interface.auto.c.inc) in each release <...> > by providing a dist tarball that contains the > generated files. This is the approach I decided to go with. In retrospect it was a mistake on my part to expose so many details of our toolchain to packaging. Live and learn! Starting with the 2.59.0 release on July 20 there will be a distribution tarball as a release asset that contains pre-built documentation in the form of HTML and a man page, help.auto.c.inc and interface.auto.c.inc pre-generated in the source tree, and a smoke test that exercises basic functionality and can be run with meson test. The test needs only the same core Python that is provided for the meson build environment. The packagers will get a consistent deliverable that we test for regressions and the pgBackRest developers can use whatever tooling is deemed best for the project, as long as it does not leak into the dist tarball. You can see an example of what the release will look like going forward (with dist tarball asset) here: https://github.com/dwsteele/pgbackrest/releases/tag/release%2F2.59.0dev This is exactly what the 2.59.0 release will look like except for the dev tag. For 2.59.0 packages can still be built as before (from a source tarball) and if there are issues with the dist tarball we will address them in patch releases before 2.60.0. I have attached the README.md that will be included in the dist tarball. It has more details on what is provided. Regards, -David
Re: Migration of pgBackRest internal support tools to Rust.
От:
David Steele <david@pgbackrest.org>
Дата:
On 7/15/26 09:44, David Steele wrote: > > My proposal is to provide the files that are currently generated at > build time (html documentation, man pages, help.auto.c.inc, > interface.auto.c.inc) in each release <...> > by providing a dist tarball that contains the > generated files. This is the approach I decided to go with. In retrospect it was a mistake on my part to expose so many details of our toolchain to packaging. Live and learn! Starting with the 2.59.0 release on July 20 there will be a distribution tarball as a release asset that contains pre-built documentation in the form of HTML and a man page, help.auto.c.inc and interface.auto.c.inc pre-generated in the source tree, and a smoke test that exercises basic functionality and can be run with meson test. The test needs only the same core Python that is provided for the meson build environment. The packagers will get a consistent deliverable that we test for regressions and the pgBackRest developers can use whatever tooling is deemed best for the project, as long as it does not leak into the dist tarball. You can see an example of what the release will look like going forward (with dist tarball asset) here: https://github.com/dwsteele/pgbackrest/releases/tag/release%2F2.59.0dev This is exactly what the 2.59.0 release will look like except for the dev tag. For 2.59.0 packages can still be built as before (from a source tarball) and if there are issues with the dist tarball we will address them in patch releases before 2.60.0. I have attached the README.md that will be included in the dist tarball. It has more details on what is provided. Regards, -David