Re: dpkg-dev: please reject native/non-native version when building native/non-native source packages
* Charles Plessy <plessy@debian.org> [140205 14:18]:
> Who benefited directly from the change of behavior ? Nobody ? Then please
> revert it; it was not necessary.
Most import are people starting to create Debian packages.
At least with 3.0 source packages they no longer have to care about the
different meanings of native vs non-native. A package either is native,
then both the version and the package reflect this, or they are
non-native. No more chances to only switch one of the fields but not the
other by mistake.
It also helps users, as it makes it easier to guess what things look
like, from only looking at the version.
Finally it makes it easier for writers of tools to deal with Debian
packages, as there are some absurd corner cases fewer. (The most absurd
one is a 3.0(quilt) with a package without hyphen. The resulting
filenames are simply ...).
> Alternatively, please rename the "3.0 (native)" format to "3.0 (tarball)" or
> anything elese, and we are done.
And brake almost everything? That suggestion is almost equivalent to
just forbidding 3.0 (native) packages completely for the next decade.
Bernhard R. Link
--
F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC
Reply to: