File: from_sources.html

package info (click to toggle)
dar 2.6.13-2
  • links: PTS
  • area: main
  • in suites: bullseye
  • size: 10,364 kB
  • sloc: cpp: 77,385; sh: 6,192; ansic: 776; makefile: 435; python: 242; csh: 95; perl: 43; sed: 16
file content (681 lines) | stat: -rw-r--r-- 29,836 bytes parent folder | download
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
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>Dar's Documentation - Compiling From Source</title></head><body style="background-color: rgb(221, 221, 221); color: rgb(0, 0, 170);" alink="#ff0000" link="#0000ff" vlink="#000055">
<center>
<div style="text-align: center;">
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="vertical-align: top; width: 161px;"><a href="index.html"><img style="border: 0px solid ; width: 160px; height: 120px;" alt="Dar Documentation" src="dar_s_doc.jpg"></a><br>
      </td>
      <td style="vertical-align: top;">
      <h1 style="text-align: center;"><br>
      </h1>
      <h1 style="text-align: center;">HOW TO COMPILE DAR AND LIBDAR<br>
      </h1>
      </td>
    </tr>
  </tbody>
</table>
</div>
<span style="font-weight: bold;"><br>
</span>
<hr style="width: 100%; height: 2px;"></center>

<br>

<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top;">
      <h3 style="font-weight: bold; text-decoration: underline;"><a name="requirements"></a>1 - Requirements</h3>
      <br>
      <div style="margin-left: 40px;">To
compile dar from a source package (from GIT <a href="#GIT">see below</a>
for additional steps)
	<span style="font-weight: bold;">you need at least</span>:<br>
      </div>
      <ol style="margin-left: 40px; text-align: justify;">
        <li>a C++ compiler supporting g++11 syntax (for <a href="http://gcc.gnu.org/">gcc</a>
that means version 4.9. minimum, <a href="http://clang.llvm.org/">clang</a> is also supported). For version older than dar-2.5.0
g++11 support is not required but if using gcc you need at least
version 3.4.x. A standard C++ library is also required, compilation has been tested with libc++ and stdlibc++.<br>
</li>
        <li>a linker like "ld" the <a href="http://www.gnu.org/software/binutils/">GNU Linker</a><br>
        </li>
        <li>make (tested with <a href="http://www.gnu.org/software/make/">gnu make</a>)</li>
      </ol>
      <div style="text-align: justify;"> </div>
      <div style="margin-left: 40px; text-align: justify;"><br>
In option you <span style="font-weight: bold;">may also have</span>
installed
the following tools and libraries:<br>
      </div>
      <div style="text-align: justify;"> </div>
      <ul style="margin-left: 40px; text-align: justify;">
        <li><a href="http://www.gzip.org/zlib/">libz library</a> for
gzip compression support
        </li>
        <li style="text-align: justify;"><a href="http://sources.redhat.com/bzip2/">libbzip2 library</a> for bzip2
compression support</li>
        <li style="text-align: justify;"><a href="http://www.oberhumer.com/opensource/lzo/">liblzo2 library</a>
for lzo compression support</li>
        <li style="text-align: justify;"><a href="http://tukaani.org/xz/">libxz library</a> for xz/lzma compression support<br>
        </li>

        <li style="text-align: justify;">gnu Getopt support (Linux has
it for all distro thanks to
its glibc, this is not true for FreeBSD for example)</li>
        <li style="text-align: justify;"><a href="http://www.gnupg.org/related_software/libraries.en.html">libgcryt</a>
version 1.4.0 or greater for symetric strong encryption (blowfish, aes,
etc.) and hash (sha1, md5) support</li>
        <li style="text-align: justify;"><a href="https://www.gnupg.org/">gpgme</a> library version 1.2.0 or greater for asymetric strong encryption and signature (RSA, DSA, etc.)<br>
        </li>

        <li style="text-align: justify;"><a href="http://www.doxygen.nl/index.html">doxygen</a>
for generation of source code documentation</li>
        <li><a href="http://upx.sourceforge.net/">upx</a> to generate
dar_suite upx compressed binaries</li>
        <li><a href="http://www.gnu.org/software/groff/groff.html">groff</a>
to generate html version of man pages</li>
        <li><a href="http://e2fsprogs.sourceforge.net">ext2/ext3/ext4 file system libraries</a> for Linux Filesystem Specific Attributes and nodump flag support<br>
        </li>

        <li><a href="http://libthreadar.sourceforge.net/">libthreadar</a> for libdar using several threads and remote repository feature (needs libcurl in addition see below)<br>
</li>
        <li><a href="http://librsync.sourceforge.net/">librsync</a> for delta binary</li>
        <li><a href="https://curl.haxx.se/libcurl/">libcurl</a> for remote repository access using ftp or sftp protocols<br></li>
	<li><a href="https://www.python.org/">python3</a> (python3-dev) and <a href="https://github.com/pybind/pybind11">pybind11</a> to access libdar from python</li>
      </ul>
      <div style="margin-left: 40px;"><br>
The consequences of building dar without these optional tools are the
following:<br>
      </div>
      <ul style="margin-left: 40px; text-align: justify;">
        <li>If you lack <span style="font-weight: bold;">libz</span>
library, dar will compile but will not be able to compress or
uncompress an archive using the gzip algorithm</li>
        <li>If you lack <span style="font-weight: bold;">libbzip2</span>
library dar will compile but will not be able to compress or uncompress
an archive using the bzip2 algorithm</li>
        <li>If you lack <span style="font-weight: bold;">liblzo2</span>
library dar will compile but will not be able to compress or uncompress
an archive using the lzo algorithm</li>
        <li>if you lack <span style="font-weight: bold;">liblzma5 </span>library dar will compile but will not be able to compress or uncompress an archive using the xz algorithm<br>
        </li>

        <li>If you lack <span style="font-weight: bold;">libgcrypt </span>dar
will still compile but you will not be able to use strong encryption
nor hash file generation for each slice</li>


        <li>if you lack <span style="font-weight: bold;">gpgme</span> dar will still compile but you will not be able to use strong encryption and signature with public keys<br>
        </li><li>If you lack <span style="font-weight: bold;">Doxygen</span>
dar will still compile but you will not have the reference
documentation for libdar after calling <span style="font-style: italic;">make</span></li>
        <li>If you lack <span style="font-weight: bold;">upx</span>
dar will still compile but the resulting binary will not be compressed
after calling <span style="font-style: italic;">make install-strip</span></li>
        <li><span style="font-style: italic;"><span style="font-style: italic;"><span style="font-style: italic;"></span></span></span>If
you lack <span style="font-weight: bold;">groff</span> dar will not
generate man pages in html format</li>
        <li>If you lack <span style="font-weight: bold;">extX file system libraries</span> you will not be able to save and restore Linux FSA, nor to avoid saving files having their nodump flag set<br>
        </li>

        <li>if you lack <span style="font-weight: bold;">libthreadar</span> libdar will execute each action in a single thread, nor you will be able to use remote ftp or sftp directly from dar<br>
</li>
        <li>if you lack <span style="font-weight: bold;">librsync</span>
library dar will still compile but you will not be able to create
archive with binary delta nor to read/restore files stored with binary
delta</li>
        <li>if you lack <span style="font-weight: bold;">libcurl</span> you won't be able to remotely read or write a archive stored using ftp or sftp<br>
        </li>
	<li>if you lack <span style="font-weight: bold;">python3</span> or <span style="font-weight: bold;">pybind11</span> you won't be able to access
	  libdar from python environment</li>
      </ul>
      <div style="text-align: justify;"><br>
      <div style="margin-left: 40px;"> </div>
      </div>
      </td>
    </tr>
  </tbody>
</table>

<br>

<div style="text-align: center;"><br>
</div>

<table style="text-align: left; width: 90%; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top;">
      <h3><a name="compiling"></a><span style="font-weight: bold; text-decoration: underline;">2 - Compilation
in brief</span></h3>
      <br>
      <div style="margin-left: 40px;">Once you have the minimum <a href="#requirements">requirements</a>, Dar has to be compiled from
source code in
the following way:<br>
      </div>
      <div style="margin-left: 80px;"><br>
      <code>./configure <a href="#configure_options">[eventually with
some options]</a><br>
make<br>
make install-strip<br>
      </code></div>
      <div style="margin-left: 40px;"><br>
      </div>
      <div style="text-align: justify; margin-left: 40px;"><span style="font-weight: bold;">Important:</span>
due to a bug in the autoconf/libtool softwares used to build the
configure script you must not have spaces in the name of the path where
are extracted dar' sources. You can install dar binary anywhere you
want, the problem&nbsp; does not concern dar itself but the ./configure
script used to build dar: To work properly it must not be ran from a
path which has a space in it.<br>
      </div>
      <div style="text-align: justify; margin-left: 40px;"><span style="font-weight: bold;">Important
too: </span>By default the configure script set optimization to -O2,
depending on the compiler this may lead to problems in the resulting
binary (or even in the compilation process), before reporting a bug try
first to compile with less optimization:<br>
      </div>
      <div style="margin-left: 40px;"><br>
      </div>
      <div style="margin-left: 80px;"><code>CXXFLAGS=-O</code><br>
      <code>export CXXFLAGS</code><br>
      <code>make clean distclean</code><br>
      <code>./configure [<a href="#configure_options">options...</a>]<br>
make<br>
      </code><code>make install-strip</code><br>
      </div>
      <div style="margin-left: 40px;"><br>
The configure script may receive several options, they are listed <a href="#configure_options">here</a>.<br>
      <br>
Note for packagers that the DESTDIR variable may be set at installation
time to install dar in another directory. This makes the creation of
dar binary packages very easy. Here is an example<br>
      <br>
      </div>
      <div style="margin-left: 80px;"><code>./configure --prefix=/usr
[eventually
with some options]</code><br>
      <code></code><code>make</code><br>
      <code>make DESTDIR=/some/where install-strip<br>
      <br>
      </code></div>
      <div style="margin-left: 40px;">This will install dar in
/some/where/usr/{bin | lib | ...}
directories. You can build a package from files under /some/where and
install/remove the package at the root of your filesystem (thus here
files will go in /usr/{bin | lib | ... }).<br>
      </div>
      <span style="font-weight: bold;"><br>
      <br>
      <br>
      </span>
      <h3><a name="configure_options"></a><span style="font-weight: bold; text-decoration: underline;">3 - Options for
the configure script</span></h3>
      </td>
    </tr>
  </tbody>
</table>

<span style="font-weight: bold; text-decoration: underline;"><br>
</span>
<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="10">

  <tbody>
    <tr>
      <td style="vertical-align: top; width: 33%;"><br>
      </td>
      <td style="vertical-align: top; font-weight: bold;">
      <h3>Available options for the
configure script</h3>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; width: 33%;"><span style="text-decoration: underline;">Optimization option:</span><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">&nbsp;--enable-mode</td>
      <td style="vertical-align: top;">&nbsp;--enable-mode=32 or
--enable-mode=infinint<br>
      <div style="text-align: justify; margin-left: 40px;">if
set,
replace 64 bits integers used by default by 32 bits integers or
"infinint" integers (limitless integers). Before release 2.6.0 the
default integer used was infinint and this option was added for speed
optimization at the cost of some limitations (See
the <a href="Limitations.html#Integers">limitations</a> for more). <br>
      <br>
Since release 2.6.0, the default is 64 bits integers (limitations stay
the same) instead of infinint. But if you hit the 64 bits integer
limitations you can still use infinint which overcome this at the cost
of slower performance and increase memory requirement.<br>
      </div>
      <br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; width: 33%;"><span style="text-decoration: underline;">Deactivation options:</span><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-largefile</td>
      <td style="vertical-align: top;">Whatever your system is, dar
will not be able to handle file of size larger than 4GB<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-ea-support<br>
      </td>
      <td style="vertical-align: top;">Whatever your system is, dar
will not be able to save or restore Extended Attributes (see the Notes
paragraphs<a href="Notes.html#I"> I</a> and <a href="Notes.html#V">V</a>)<br>
      <br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-nodump-flag<br>
      </td>
      <td style="vertical-align: top;">Whatever your system is, dar
will not be able to take care of the nodump-flag (thanks to the
--nodump option)<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-dar-static<br>
      </td>
      <td style="vertical-align: top;"><span style="font-style: italic;">dar_static</span>
binary (statically linked version of dar) will not be built<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-special-alloc<br>
      </td>
      <td style="vertical-align: top; text-align: justify;">dar uses a
special allocation scheme by default (gather the many small allocations
in big fewer ones), this improves dar's execution speed<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-upx<br>
      </td>
      <td style="vertical-align: top;">If <span style="font-style: italic;">upx</span> is found in the PATH, binary
are upx compressed at installation step. This can be disabled by this
option, when upx is available and you don't want compressed binaries.<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-gnugetopt<br>
      </td>
      <td style="vertical-align: top;">&nbsp;on non GNU systems
(Solaris, etc.) configure looks for libgnugetopt to have the long
options support thanks to the gnu getopt_long() call, this can be
disabled.<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-thread-safe<br>
      </td>
      <td style="vertical-align: top; text-align: justify;">&nbsp;libdar
may need <span style="font-style: italic;">POSIX mutex</span> to be
thread safe. If you don't want libdar relaying on <span style="font-style: italic;">POSIX mutex</span> even if they are
available, use this option. The resulting library may not be thread
safe. But it will always be thread safe if you use
--disable-special-alloc, and it will never be thread safe if
--enable-test-memory is used.<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-libdl-linking<br>
      </td>
      <td style="vertical-align: top;">Ignore any libdl library and
avoid linking with it<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-libz-linking<br>
      </td>
      <td style="vertical-align: top;">Disable linking to libz, thus
-zgzip:*
option (gzip compression) will not be available<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-libbz2-linking<br>
      </td>
      <td style="vertical-align: top;">Disable linking to libbz2, thus
-zbzip2:* option (libbz2 compression) will not be available<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-liblzo2-linking<br>
      </td>
      <td style="vertical-align: top;">Disable linking to liblzo2, thus
-zlzo:* option (lzo compression) will not be available<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-libxz-linking<br>
      </td>
      <td style="vertical-align: top;">Disable linking to liblzma5 this -zxz:* option (xz compression) will not be available<br>
      </td>
    </tr>
<tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-libgcrypt-linking<br>
      </td>
      <td style="vertical-align: top; text-align: justify;">Disable
linking with libgcrypt library. Strong encryption will not be
available neither a hashing of generated slices.<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-gpgme-linking<br>
      </td>
      <td style="vertical-align: top;">Disable
linking with gpgme library. Asymetric strong encryption algorithms will not be available<br>
      </td>
    </tr>
<tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--disable-build-html<br>
      </td>
      <td style="vertical-align: top;">Do not build API documentation
reference with Doxygen (when it is available)<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-furtive-read<br>
      </td>
      <td style="vertical-align: top;">Do not try to detect whether the
system does support furtive read mode. This will lead furtive read
mode to stay disabled in any case.<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">&nbsp;--disable-fast-dir<br>
      </td>
      <td style="vertical-align: top;">Disable optimization for large
directories, doing so has a little positive impact on memory
requirement but a huge drawback on execution time<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-execinfo<br>
      </td>
      <td style="vertical-align: top;">Disable reporting stack
information on self diagnostic bugs even<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-threadar<br>
      </td>
      <td style="vertical-align: top;">Avoid linking with libthreadar even if available, libdar will not create threads<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-birthtime<br>
      </td>
      <td style="vertical-align: top;">Disable the HFS+ Filesystem Specific Attribute support<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-librsync-linking<br>
      </td>
      <td style="vertical-align: top;">Disable linking with librsync, thus delta binary will not be available<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--disable-libcurl-linking<br>
      </td>
      <td style="vertical-align: top;">Disable linking with libcurl, thus remote repository support using ftp or sftp will not be available<br>
      </td>
    </tr>
<tr>
      <td style="vertical-align: top; width: 33%;"><span style="text-decoration: underline;">Troubleshooting option:</span><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--enable-os-bits<br>
      </td>
      <td style="vertical-align: top; text-align: justify;">If set, dar
uses the given argument (32 or 64) to determine which integer type to
use. This much match your CPU register size. By default dar uses the
system &lt;stdint.h&gt; file to determine the correct integer type to
use<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; width: 33%;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; width: 33%;"><span style="text-decoration: underline;">Debugging options:</span><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--enable-examples<br>
      </td>
      <td style="vertical-align: top; text-align: justify;">If set,
example programs based on infinint will also be built<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--enable-debug<br>
      </td>
      <td style="vertical-align: top;">If set, use debug compilation
option, and if possible statically link binaries<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--enable-pedantic<br>
      </td>
      <td style="vertical-align: top; text-align: justify;">If set,
transmits the -pedantic option to the compiler<br>
      </td>
    </tr>

    <tr>
      <td style="vertical-align: top; text-align: right; width: 33%;">--enable-profiling<br>
      </td>
      <td style="vertical-align: top;">Enable executable profiling<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top; text-align: right;">--enable-debug-memory<br>
      </td>
      <td style="vertical-align: top;">If set, logs all memory
allocations and releases to /tmp/dar_debug_mem_allocation.txt&nbsp; .
The
resulting executable is expected to be very slow<span style="font-weight: bold;"></span><br>
      </td>
    </tr>
  </tbody>
</table>

<br>

<br>

<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top; text-align: justify;">
      <h3 style="text-decoration: underline;"><a name="GIT"></a>4 - GIT</h3>
      <h3><br>
      </h3>
      <h3 style="margin-left: 40px;">Presentation</h3>
      <div style="margin-left: 80px;">To
manage its source code
versions DAR uses GIT (it used CVS up to Q1 2012 and even the older RCS
in 2002). Since September 2nd 2017, the GIT repository has been cloned
to <a href="https://github.com/Edrusb/DAR">GitHub</a> while the original repository <a href="https://sourceforge.net/p/dar/code/">at Sourceforge</a> still stays updated. Both
should contain the exact same code, that's up to you to choose the repository you
prefer. For sanity also, starting September 3rd 2017, git tags including those for release candidates will be signed with GPG.<br>
      </div>
      <h3 style="margin-left: 40px;">Dar's repository Organization</h3>
      <div style="margin-left: 80px;">GIT (more than CVS) eases the use
of branches. In dar repository, there are thus a lot of them: the first
and main one is called "master". It contains current development and
most probably unstable code. There are other permanent branches that
hold stable code. They are all named by "<span style="font-weight: bold;">branch_A.B.x</span>" where A and B are the
numbers corresponding to a released versions family. For example, "<span style="font-weight: bold;">branch_2.6.x</span>" holds the stable code
for releases 2.6.0, 2.6.1, 2.6.2 and so on. <span style="text-decoration: underline;">It also holds pending fixes for
the next release on that branch you might be interested in.</span> <br>
      <br>
The global organisation of the repository is thus the following:<br>
&nbsp;<br>
      <code>&nbsp;<br>
&nbsp;(HEAD of "master" branch)<br>
&nbsp;&nbsp;&nbsp; new feature 101<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ^<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; new feature 100<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ^<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; new feature 99<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +---&gt;-- fix
901 -&gt;- fix 902 (release 2.4.1) -&gt;- fix 903 -&gt;- fix 904
(release 2.4.2) -&gt;- fix 905 (HEAD of branch_2.4.x)<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; new feature 98<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ^<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; new feature 97<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; +---&gt;-- fix 801 -&gt;-
fix 802 (release 2.3.1) (also HEAD of branch_2.3.x as no pending fix is
waiting for release)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ^<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp; initial version<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ____<br>
      </code>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>
      <br>
      </div>
      <h3 style="margin-left: 40px;">Usage</h3>
      <div style="margin-left: 80px;">To get dar source code from GIT
you have first to <span style="font-weight: bold;">clone</span> the
repository hosted at sourceforge:<br>
      <br>
      </div>
      <div style="margin-left: 120px;"><span style="font-family: monospace;"></span><code>git clone https://github.com/Edrusb/DAR.git<br>
cd DAR<br>
      </code> </div>
      <div style="margin-left: 80px;"><br>
You will probably not want to use current development code so you have
to change from the branch <span style="font-style: italic;">master</span>
to the branch "branch_A.B.x" of you choice:<br>
      <br>
      </div>
      <div style="margin-left: 120px;"><code></code><code>git checkout
branch_2.6.x<br>
      </code> </div>
      <div style="margin-left: 80px;"><br>
That's all. You now have the most recent stable code (for branch_2.6.x
in this example). To see what changes have been brought since the last
release, use the following command:<br>
      <br>
      </div>
      <div style="margin-left: 120px;"><code>git log</code><br>
      </div>
      <div style="margin-left: 80px;">&nbsp;<br>
If you plan to keep the repository you've cloned, updating the change
is as easy as using (no need to clone the repository from scratch
again):&nbsp; <code></code><br>
      <br>
      </div>
      <div style="margin-left: 120px;"><code>git pull</code><code></code>
      </div>
      <div style="margin-left: 80px;"><br>
There is also a web interface to git at <a href="https://github.com/Edrusb/DAR">github</a><br>
      </div>
      <h3 style="margin-left: 40px;"><span style="font-weight: bold;">Having
the sources ready for compilation</span></h3>
      <div style="margin-left: 80px;"><span style="font-family: monospace;"></span>Please
read the fiile named "USING_SOURCE_FROM_GIT" located at the root of the
directory tree you retrieved through GIT, it contains up to date
information about the required tools and how to generate the
configuration file. Then you can proceed to source compilation as <a href="#compiling">done with regular source package</a>. <br>
      </div>
      <br>
      </td>
    </tr>
  </tbody>
</table>

<br>
<table style="width: 90%; text-align: left; margin-left: auto; margin-right: auto;" border="0" cellpadding="2" cellspacing="2">

  <tbody>
    <tr>
      <td style="vertical-align: top;"><span style="font-weight: bold; text-decoration: underline;"></span>
      <div style="text-align: justify;">
      <h3><a style="font-weight: bold; text-decoration: underline;" name="Tools_sites">5 - Related Softwares</a></h3>
      <blockquote>
        <ul>
          <li><a href="http://www.gnu.org/software/tar/tar.html">TAR
home
page</a> (DAR's grant and venerable brother) </li>
          <li><a href="http://acl.bestbits.at/">Extended Attributes</a>
home page </li>

          <li><a href="http://www.gnupg.org/">GNU Privacy Guard</a>
home
page </li>
          <li><a href="http://cygwin.com/">Cygwin</a> home page </li>
          <li><a href="http://parchive.sourceforge.net/">Parchive</a>
home
page and <a href="https://github.com/BlackIkeEagle/par2cmdline">https://github.com/BlackIkeEagle/par2cmdline</a>
(fork from the official site maintained since decembre 2013) </li>
          <li><a href="http://upx.sourceforge.net/">the Ultimate Packer
for
eXecutables</a> home page </li>
          <li><a href="http://www.doxygen.org/">Doxygen</a> home page</li>
          <li><a href="http://www.gnu.org/software/groff/groff.html">Groff</a>
home page</li>
          <li><a href="http://www.gnu.org/software/make/">Gnu Make</a>
home page</li>
          <li><a href="http://gcc.gnu.org/">GCC</a> home page<br>
          </li>
        </ul>
      </blockquote>
      <br>
      </div>
      </td>
    </tr>
  </tbody>
</table>

<br>

<br>


</body></html>