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 <jrf@mailbox.org>
This commit is contained in:
Xi Ruoyao 2024-12-11 20:31:08 +08:00
parent 6fa6a4f3ce
commit eb35057724
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3

View File

@ -22,8 +22,9 @@
<para>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 <command>configure</command> 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 <command>configure</command> script generated by
<command>autoconf</command>), 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