From eb3505772428ea2d77430e03da2ebeb0dfdbd9bd Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Wed, 11 Dec 2024 20:31:08 +0800 Subject: [PATCH] packages: Reword release tarball vs repo snapshot difference Besides Rainer's suggestion, also use a vague "not stored in the repository" instead of the over-precise "generated": there are also vendored external source copies (as Git submodules or manually embedded during Release Engineering, for example the gnulib copies in many GNU packages); and maybe other cases. Suggested-by: Rainer Fiebig --- chapter03/introduction.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/chapter03/introduction.xml b/chapter03/introduction.xml index 05488ecbc..645686311 100644 --- a/chapter03/introduction.xml +++ b/chapter03/introduction.xml @@ -22,8 +22,9 @@ For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with - similar file names. A release tarball contains generated files (for - example, a configure script generated by + similar or even identical file names. But the release tarball may contain + some files which are essential despite not stored in the repository + (for example, a configure script generated by autoconf), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release