RPM packaging (was: Last set of changes for 1.1.3)

[Sandworm]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, 29 August 2006 7:01 PM, Nicolas Baradakis wrote:

>
> Thanks for the explanation: I never used rpmbuild myself, so I
didn't
> know the detailed mechanisms. Then it appears deletion is not
really
> a problem. The only thing that is strange, is that you redo with
> rpmbuild what the Makefile has already done.
>

The RPM build process does use the Makefile. It does a complete
build and install, but does the install in the environment of
the "build root", which has a usr, etc, bin, and so on. The built
directory is then used to construct the packaged binary RPM
(and source RPM, if requested). However, it needs to distinguish
between different types of files. This is why files are tagged as
"%doc", because these need to be located in what is designated as
the documentation directory.

So, regardless of the original directory that the Makefile
installed them in, they get moved into the documentation
directory, sort of relative to the way they are specified in
the %doc directives.

If you're interested, see "The %doc Directive" at
http://www.rpm.org/max-rpm/s1-rpm-inside-files-list-
directives.html.

Regards
SW
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.5

wkYEARECAAYFAkT1SdEACgkQmw4BJyaatJ0eVgCgoM2ZJElpezgs821HUu6lfa1YUFgA
oKWP1VLiIBUuZ3CXU3aiCZwQK74S
=i+p9
-----END PGP SIGNATURE-----