/usr/share/doc/lintian/lintian.html/section-1.2.html is in lintian 2.5.43.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>The intention of Lintian</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Lintian User's Manual"
HREF="index.html"><LINK
REL="UP"
TITLE="Introduction"
HREF="chapter-1.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
HREF="chapter-1.html"><LINK
REL="NEXT"
TITLE="Design issues"
HREF="section-1.3.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Lintian User's Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="chapter-1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. Introduction</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="section-1.3.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="section-1.2"
>1.2. The intention of Lintian</A
></H1
><P
> Packaging has become complicated—not because dpkg is
complicated (indeed, dpkg-deb is very simple to use) but
because of the high requirements of our policy. If a developer
releases a new package, she has to consider hundreds of
guidelines to make the package `policy compliant.'
</P
><P
> All parts of our policy have been introduced by the same procedure:
Some developer has a good idea how to make packages more `unique' with
respect to a certain aspect—then the idea is discussed and a policy
proposal is prepared. If we have a consensus about the policy change,
it's introduced in our manuals.
</P
><P
> Therefore, our policy is <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>not</I
></SPAN
> designed to
make life harder for the maintainers! The intention is to make
Debian the best Linux distribution out there. With this in
mind, lots of policy changes are discussed on the mailing
lists each week.
</P
><P
> But changing the policy is only a small part of the story:
Just having some statement included in the manual does not
make Debian any better. What's needed is for that policy to
become `real life,' i.e.,
it's <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>implemented</I
></SPAN
> in our packages. And
this is where Lintian comes in: Lintian checks packages and
reports possible policy violations. (Of course, not everything
can be checked mechanically — but a lot of things can
and this is what Lintian is for.)
</P
><P
>Thus, Lintian has the following goals:</P
><P
></P
><UL
><LI
STYLE="list-style-type: disc"
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>To give us some impression of the `gap'
between theory (written policy) and praxis (current state of
implementation).</I
></SPAN
>
</P
><P
> From the results of the first two Lintian checks I
implemented, I see that there is a big need to make this
gap smaller. Introducing more policy aspects is worthless
unless they are implemented. We first should fix packages
to comply with current policy before searching for new
ways to make policy more detailed. (Of course, there are
also important policy changes that need to be introduced
— but this is not what's meant here.)
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
> To make us re-think about certain aspects of our policy.
</I
></SPAN
>
</P
><P
> For example, it could turn out that some ideas that once
sounded great in theory are hard to implement in all our
packages — in which case we should rework this
aspect of policy.
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
> To show us where to concentrate our efforts in order to
make Debian a higher quality distribution.
</I
></SPAN
>
</P
><P
> Most release requirements will be implemented through
policy. Lintian reports provide an easy way to
compare <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>all</I
></SPAN
> our packages against
policy and keep track of the fixing process by watching
bug reports. Note, that all this can be
done <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>automatically</I
></SPAN
>.
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
><SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>To make us avoid making the same mistakes all over again.</I
></SPAN
>
</P
><P
> Being humans, it's natural for us to make errors. Since we
all have the ability to learn from our mistakes, this is
actually no big problem. Once an important bug is
discovered, a Lintian check could be written to check for
exactly this bug. This will prevent the bug from appearing
in any future revisions of any of our packages.
</P
></LI
></UL
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="chapter-1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="section-1.3.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="chapter-1.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Design issues</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
|