Gab's eigentlich eine nachvollziehbare Begründung dafür, warum die Revision eines selbstkompilierten Debian-Linux-Kerns mittlerweile unbedingt mit einer Zahl beginnen muss? Ich darf jetzt wegen eines Popelbuchstabens den funktionierenden Kern nochmal kompilieren. (Wäre vielleicht auch anders gegangen, aber so fit bin ich nicht, also nochmal )
Grüße, Günther
Revisionskennung
-
- Beiträge: 2951
- Registriert: 24.12.2010 16:50:59
- Lizenz eigener Beiträge: MIT Lizenz
- Wohnort: Rheinland
Re: Revisionskennung
Das wurde gemacht, um dich zu aergern. Es musste halt einmal festgelegt werden. Hier ist es definiert:
http://www.debian.org/doc/debian-policy ... ields.html
http://www.debian.org/doc/debian-policy ... ields.html
Du hast dich einfach nicht dran gehalten. Lektion gelernt.debian_revision
This part of the version number specifies the version of the Debian package based on the upstream version. It may contain only alphanumerics and the characters + . ~ (plus, full stop, tilde) and is compared in the same way as the upstream_version is.
It is optional; if it isn't present then the upstream_version may not contain a hyphen. This format represents the case where a piece of software was written specifically to be a Debian package, where the Debian package source must always be identical to the pristine source and therefore no revision indication is required.
It is conventional to restart the debian_revision at 1 each time the upstream_version is increased.
The package management system will break the version number apart at the last hyphen in the string (if there is one) to determine the upstream_version and debian_revision. The absence of a debian_revision is equivalent to a debian_revision of 0.
When comparing two version numbers, first the epoch of each are compared, then the upstream_version if epoch is equal, and then debian_revision if upstream_version is also equal. epoch is compared numerically. The upstream_version and debian_revision parts are compared by the package management system using the following algorithm:
The strings are compared from left to right.
First the initial part of each string consisting entirely of non-digit characters is determined. These two parts (one of which may be empty) are compared lexically. If a difference is found it is returned. The lexical comparison is a comparison of ASCII values modified so that all the letters sort earlier than all the non-letters and so that a tilde sorts before anything, even the end of a part. For example, the following parts are in sorted order from earliest to latest: ~~, ~~a, ~, the empty part, a.[37]
Then the initial part of the remainder of each string which consists entirely of digit characters is determined. The numerical values of these two parts are compared, and any difference found is returned as the result of the comparison. For these purposes an empty string (which can only occur at the end of one or both version strings being compared) counts as zero.
These two steps (comparing and removing initial non-digit strings and initial digit strings) are repeated until a difference is found or both strings are exhausted.
Note that the purpose of epochs is to allow us to leave behind mistakes in version numbering, and to cope with situations where the version numbering scheme changes. It is not intended to cope with version numbers containing strings of letters which the package management system cannot interpret (such as ALPHA or pre-), or with silly orderings.[38]
Re: Revisionskennung
Willste mir jetzt Englisch beibringen? Frau! Das artet ja in Arbeit aus!
Überflogen habe ich's Aber die Zeile(n) mit der notwendigen Nummer habe ich noch nicht gecheckt.
Grüße, Günther
Überflogen habe ich's Aber die Zeile(n) mit der notwendigen Nummer habe ich noch nicht gecheckt.
Grüße, Günther
-
- Beiträge: 2951
- Registriert: 24.12.2010 16:50:59
- Lizenz eigener Beiträge: MIT Lizenz
- Wohnort: Rheinland
Re: Revisionskennung
Klein Fleiß, kein Preis!