@dralley commented on this pull request.
>
```
00000000: ed ab ee db 03 00 00 00
```
-The first 4 bytes (0-3) are "magic" used to uniquely identify an RPM
-package. It is used by RPM and file(1). The next two bytes (4, 5)
-are int8 quantities denoting the "major" and "minor" RPM file format
-version. This package is in 3.0 format. The following 2 bytes (6-7)
-form an int16 which indicates the package type. As of this writing
-there are only two types: 0 == binary, 1 == source.
+The first 4 bytes (0-3) are the "magic" number used to uniquely identify a file
+as an RPM package. It is used by RPM and file(1). The next two bytes (4, 5)
+are int8 quantities denoting the "major" and "minor" RPM file format version.
+For legacy reasons, this version is always "3.0" (major version "3", minor
+version "0"), even with packages built by RPM 4.0+ (referred to as RPM v4
+packages). The following 2 bytes (6-7) form an int16 which indicates the
+package type. As of this writing there are only two types: 0 == binary,
+1 == source.
Sometimes it's hard to tell what changed apart from the line wrapping, but
there are wording adjustments in here I promise :)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835#pullrequestreview-1807603861
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2835/review/1807603...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
