>>>>> "Martin" =3D=3D Martin v L=F6wis <martin@v.loewis.de> writes:
Martin> Skip Montanaro wrote:
>> Ah, but now you have a "machine" that will generate the bit of d=
ocumentation
>> you desire as part of the install process (binary or source).
Martin> The question still is what is easiest for people producing
Martin> Python binaries. Do they want to paste files from the CVS t=
o
Martin> fulfill the requirements, or would they prefer to print a
Martin> variable in Python?
You simply have an automated post-install or binary distro build step w=
hich
does the little find-the-copyrights dance and dumps the result to somet=
hing
like LICENSES.txt or LICENSES.tex or LICENSES.hlp in the appropriate
directory and either declare it to be documentation or incorporate it i=
nto
the documentation delivered with the distribution.
People distributing Python with another package will have to do this so=
rt of
thing themselves, but that's not our concern.
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4