Hello, Thank you for the discussion, Ian and Simon. Here is the beginnings of a patch:
> diff --git a/policy/ch-source.rst b/policy/ch-source.rst > index 9e7d79c..f27226e 100644 > --- a/policy/ch-source.rst > +++ b/policy/ch-source.rst > @@ -40,9 +40,15 @@ example, if building a package requires a certain > compiler, then the > compiler should be specified as a build-time dependency. > > It is not necessary to explicitly specify build-time relationships on a > -minimal set of packages that are always needed to compile, link and put > -in a Debian package a standard "Hello World!" program written in C or > -C++. The required packages are called *build-essential*, and an > +minimal set of packages that are always needed > + > +- to compile, link and put in a Debian package a standard "Hello > + World!" program written in C or C++; and > + > +- for the package build to resolve the system hostname to a > + fully-qualified domain name using the C standard library. [#]_ > + > +The required packages are called *build-essential*, and an > informational list can be found in > ``/usr/share/doc/build-essential/list`` (which is contained in the > ``build-essential`` package). [#]_ > @@ -757,6 +763,10 @@ according to this convention, the C source code of an > executable > ``debian/missing-sources/checksum/util.c``. > > .. [#] > + The functionality described in this last list item is provided by > + the "netbase" package at the time of writing. > + > +.. [#] > Rationale: > > - This allows maintaining the list separately from the policy Ian also thinks that package builds should be able to access the information normally contained in /etc/protocols and /etc/services by means of the C standard library. Could you say more about why this is needed, and provide wording for a third bullet point in the list in my patch, which describes the functionality of /etc/protocols and /etc/services, please? -- Sean Whitton
signature.asc
Description: PGP signature
