25
25
26
26
< a name ="toc "> </ a >
27
27
< div class ="box " id ="toc-box ">
28
- < h1 > Contents</ h1 >
28
+ < h1 class =" header " > Contents</ h1 >
29
29
< ul id ="toc ">
30
30
< li > < a href ="#package-managers "> Packages & Package Managers</ a > </ li >
31
31
< ul >
@@ -47,7 +47,7 @@ <h1>Contents</h1>
47
47
48
48
< a name ="package-managers "> </ a >
49
49
< div class ="box ">
50
- < h1 class ="section- header "> < a href ="#toc-box "> Packages & Package Managers</ a > </ h1 >
50
+ < h1 class ="header "> < a href ="#toc-box "> Packages & Package Managers</ a > </ h1 >
51
51
52
52
< p >
53
53
Most Linux and BSD based operating systems use
@@ -59,7 +59,7 @@ <h1 class="section-header"><a href="#toc-box">Packages & Package Managers</a
59
59
</ p >
60
60
61
61
< a name ="binary-packages "> </ a >
62
- < h2 > Binary Packages</ h2 >
62
+ < h2 class =" header " > Binary Packages</ h2 >
63
63
64
64
< p >
65
65
The term "binary package" refers to a software archive assembled for deployment & active
@@ -69,7 +69,7 @@ <h2>Binary Packages</h2>
69
69
</ p >
70
70
71
71
< a name ="source-packages "> </ a >
72
- < h2 > Source Packages</ h2 >
72
+ < h2 class =" header " > Source Packages</ h2 >
73
73
< p >
74
74
Source packages require steps to prepare the contents for system use. Often part of the
75
75
process includes compiling text source code into machine code to be executed on the host
@@ -81,7 +81,7 @@ <h2>Source Packages</h2>
81
81
</ p >
82
82
83
83
< a name ="debreates-role "> </ a >
84
- < h2 > Debreate's Role</ h2 >
84
+ < h2 class =" header " > Debreate's Role</ h2 >
85
85
< p >
86
86
As of yet, Debreate does not support creating source packages or the creation of binary
87
87
packages from source. It is currently only capable of the manual creation of .deb packages
@@ -91,9 +91,9 @@ <h2>Debreate's Role</h2>
91
91
92
92
< a name ="ui "> </ a >
93
93
< div class ="box ">
94
- < h1 > < a href ="#toc-box "> Debreate's UI</ a > </ h1 >
94
+ < h1 class =" header " > < a href ="#toc-box "> Debreate's UI</ a > </ h1 >
95
95
96
- < h2 > Startup</ h2 >
96
+ < h2 class =" header " id =" ui-startup " > Startup</ h2 >
97
97
< p >
98
98
If the app's configuration file is not found on the system a dialog will display with a
99
99
first time run message. A new configuration with default values will be created in
@@ -118,7 +118,7 @@ <h2>Startup</h2>
118
118
119
119
< a name ="control "> </ a >
120
120
< div class ="box ">
121
- < h1 > < a href ="#toc-box "> Control File</ a > </ h1 >
121
+ < h1 class =" header " > < a href ="#toc-box "> Control File</ a > </ h1 >
122
122
< p >
123
123
.deb packages contain the file < tt > DEBIAN/control</ tt > . This file contains meta information
124
124
about the package. Such as the package name, package version, author, & requirements.
@@ -150,7 +150,7 @@ <h1><a href="#toc-box">Control File</a></h1>
150
150
151
151
< a name ="depends "> </ a >
152
152
< div class ="box ">
153
- < h1 > < a href ="#toc-box "> Dependencies & Conflicts</ a > </ h1 >
153
+ < h1 class =" header " > < a href ="#toc-box "> Dependencies & Conflicts</ a > </ h1 >
154
154
155
155
< p >
156
156
Though on a separate page, dependencies & conflicts are part of the control file.
@@ -184,7 +184,7 @@ <h1><a href="#toc-box">Dependencies & Conflicts</a></h1>
184
184
185
185
< a name ="files "> </ a >
186
186
< div class ="box ">
187
- < h1 > < a href ="#toc-box "> Files</ a > </ h1 >
187
+ < h1 class =" header " > < a href ="#toc-box "> Files</ a > </ h1 >
188
188
189
189
< p >
190
190
This section is for the main contents of the package that will be installed to the target
@@ -218,7 +218,7 @@ <h1><a href="#toc-box">Files</a></h1>
218
218
219
219
< a name ="scripts "> </ a >
220
220
< div class ="box ">
221
- < h1 > < a href ="#toc-box "> Scripts</ a > </ h1 >
221
+ < h1 class =" header " > < a href ="#toc-box "> Scripts</ a > </ h1 >
222
222
223
223
< p >
224
224
Debian packages support four scripts that are executed at different points during the
@@ -261,9 +261,7 @@ <h1><a href="#toc-box">Scripts</a></h1>
261
261
delete the link upon uninstalling the package.
262
262
</ p >
263
263
264
- < p >
265
- < b > How to use Auto-Link:</ b >
266
- </ p >
264
+ < p class ="header "> How to use Auto-Link:</ p >
267
265
268
266
< p >
269
267
Press the < img src ="/res/button/import.png " title ="import "> button to copy any executables
@@ -278,7 +276,7 @@ <h1><a href="#toc-box">Scripts</a></h1>
278
276
279
277
< a name ="changelog "> </ a >
280
278
< div class ="box ">
281
- < h1 > < a href ="#toc-box "> Changelog</ a > </ h1 >
279
+ < h1 class =" header " > < a href ="#toc-box "> Changelog</ a > </ h1 >
282
280
283
281
< p >
284
282
A changelog file is not required by Debian policy, but is useful to inform users of fixes
@@ -298,7 +296,7 @@ <h1><a href="#toc-box">Changelog</a></h1>
298
296
299
297
< a name ="copyright "> </ a >
300
298
< div class ="box ">
301
- < h1 > < a href ="#toc-box "> Copyright</ a > </ h1 >
299
+ < h1 class =" header " > < a href ="#toc-box "> Copyright</ a > </ h1 >
302
300
303
301
< p >
304
302
Inclusion of a copyright/license file notifies end users of how the software they are
@@ -334,7 +332,7 @@ <h1><a href="#toc-box">Copyright</a></h1>
334
332
335
333
< a name ="menu "> </ a >
336
334
< div class ="box ">
337
- < h1 > < a href ="#toc-box "> Menu</ a > </ h1 >
335
+ < h1 class =" header " > < a href ="#toc-box "> Menu</ a > </ h1 >
338
336
339
337
< p >
340
338
This section is for an optional menu entry to be included with the package. Adding a menu
@@ -367,7 +365,7 @@ <h1><a href="#toc-box">Menu</a></h1>
367
365
368
366
< a name ="build "> </ a >
369
367
< div class ="box ">
370
- < h1 > < a href ="#toc-box "> Build</ a > </ h1 >
368
+ < h1 class =" header " > < a href ="#toc-box "> Build</ a > </ h1 >
371
369
372
370
< a class ="app-screen " href ="/res/screenshot/09-build.png "> </ a >
373
371
0 commit comments