/usr/share/doc/lintian/lintian.html/section-1.3.html is in lintian 2.5.30+deb8u4.
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 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Design issues</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="The intention of Lintian"
HREF="section-1.2.html"><LINK
REL="NEXT"
TITLE="Disclaimer"
HREF="section-1.4.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="section-1.2.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.4.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="section-1.3"
>1.3. Design issues</A
></H1
><P
>There are three fields of application for Lintian:</P
><P
></P
><UL
><LI
STYLE="list-style-type: disc"
><P
> one person could use Lintian to check the whole Debian
archive and reports bugs,
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> each maintainer runs Lintian over her packages before
uploading them,
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> dinstall checks packages which are uploaded to master
before they are installed in the archive.
</P
></LI
></UL
><P
> The authors of Lintian decided to use a very modular design to
achieve the following goals:
</P
><P
></P
><UL
><LI
STYLE="list-style-type: disc"
><P
> flexibility: Lintian can be used to check single packages
or the whole archive and to report and keep track of bug
reports, etc.
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> completeness: Lintian will eventually include checks for
(nearly) everything that can be checked mechanically.
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> uptodateness: Lintian will be updated whenever policy is
changed.
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> performance: Lintian should make it possible to check
single packages within seconds or check the full archive
within 5 days.
</P
></LI
></UL
><P
> The design also has a number of constrains that limits the
things Lintian can check for and what tools it can use:
</P
><P
></P
><UL
><LI
STYLE="list-style-type: disc"
><P
> static analysis: The code in a package may be analyzed,
but it should <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>never</I
></SPAN
> be executed.
However, Lintian can (and does) use external tools to
analyze files in the package.
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> deterministic replay-ability: Checks should not rely on
the state of system caches or even the system time. These
things makes it harder for others to reproduce (the
absence of) tags.
</P
></LI
><LI
STYLE="list-style-type: disc"
><P
> same source analysis: Lintian checks packages in small
isolated groups based on the source package. Requiring
the presence of all the dependencies to provide the full
results make it harder to run lintian (not to mention, it
makes "deterministic replay-ability" a lot harder as
well).
</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="section-1.2.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.4.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The intention of Lintian</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"
>Disclaimer</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
|