Re: Upstream maintainer adding debian/rules
On Fri, 06 Nov 1998, Shaleh wrote:
> > This has the benefit, that someone else can become Debian
> > maintainer of the package and change minor policy bugs. This
> > Debian maintainer wouldn't have to do much, but only fix some
> > problems and create an official Debian binary.
> > Other native Debian packages like alien, apt, dpkg,... also don't
> > have a "build number", so why should this package have some?
> The package build number is a standard practive among many debian
> packages. It allows for you to fix packaging bugs w/o touching the
> version number of the software itself.
Maybe you miss understood the definition of the Debian version
numbering scheme? The packaging manual tells us the following:
5. Version numbering
--------------------
[...]
The version number format is:
[<epoch>`:']<upstream-version>[`-'<debian-revision>].
The three components here are:
[...]
<upstream-version>
This is the main part of the version. It is usually version
number of the original (`upstream') package of which the `.deb'
file has been made, if this is applicable.
[...]
<debian-revision>
This part of the version represents the version of the
modifications that were made to the package to make it a Debian
binary package. It is in the same format as the
<upstream-version> and dpkg compares it in the same way.
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 turned into a
Debian binary package, and so there is only one `debianization'
of it and therefore no revision indication is required.
So "-1" isn't the "build number" like you called it, but the
"debian-revision". And this Debian revision is optional and it is only
used to show the modifications between the upstream version and the
debian version. If upstream author and Debian maintainer are the same
person, the debian-revision isn't needed.
And if the upstream author adds a debian-revision there is no chance
for a Debian maintainer (who may have to fix some bugs to become
policy conformant), because this Debian maintainer isn't able to add
another debian-revision, but only a non-maintainer debian revision -1.1
> Not a necessary thing, but a good idea none the less.
Don't think so in this situation.
Ciao
Roland
--
* Internet: roland@spinnaker.rhein.de * Fido: 2:2450/42 *
PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF
Reply to: