Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e")
On Wed, Jun 04, 2003 at 05:12:34PM -0500, John Hasler wrote:
> mdz writes:
> > Do we need to legislate good sense now?
>
> If you want all bug closures mentioned in the Debian changelog, change
> policy so that it says so. I read the present policy document as requiring
> that the Debian changelog mention only changes to the Debian-specific part
> of the package. If this is not what you mean, clarify it.
The policy manual isn't a general mechanism for attempting to control
developer behaviour; it serves a specific purpose in providing a standard
for package integration.
http://www.debian.org/doc/debian-policy/ch-scope.html#s1.1
This manual describes the policy requirements for the Debian GNU/Linux
distribution. This includes the structure and contents of the Debian archive
and several design issues of the operating system, as well as technical
requirements that each package must satisfy to be included in the distribution.
This manual also describes Debian policy as it relates to creating Debian
packages. It is not a tutorial on how to build packages, nor is it exhaustive
where it comes to describing the behavior of the packaging system. Instead,
this manual attempts to define the interface to the package management system
that the developers have to be conversant with.[1]
[1] Informally, the criteria used for inclusion is that the material meet one
of the following requirements:
Standard interfaces
The material presented represents an interface to the packaging system that
is mandated for use, and is used by, a significant number of packages, and
therefore should not be changed without peer review. Package maintainers can
then rely on this interfaces not changing, and the package management software
authors need to ensure compatibility with these interface definitions. (Control
file and changelog file formats are examples.)
Chosen Convention
If there are a number of technically viable choices that can be made, but
one needs to select one of these options for inter-operability. The version
number format is one example.
--
- mdz
Reply to: