On Mon, 05 Jul 2010, Russ Allbery wrote:
> Well, they do, in that binNMUs do change the changelog included in
> the package. I'm inclined to agree that it's not a big deal if we
> lose that information in the installed package, though.
Right; this is kind of an odd thing, because a binNMU has a source
version which doesn't match the entry in the changelog.
> any -> any can use (= ${binary:Version})
> any -> all can use (= ${source:Version})
> all -> all can use (= ${source:Version})
>
> The question is what to do for all -> any. Right now, I think best
> practice is to do something like:
>
> (>= ${source:Version}), (<< ${source:Version}+b99)
In general, if you had an arch all package which had to be installed,
it should have the changelog in it, and the arch any package wouldn't.
The only exception I can see is a case where the arch: all package
wouldn't be a dependency of the arch: any package, but the arch: all
package requires functionality in the arch: any package (and there
isn't any required arch: all package from the same source). [Like a
source package which builds a core set of binaries, and an -examples
package of perl scripts which needs the core set to function.]
Don Armstrong
--
Personally, I think my choice in the mostest-superlative-computer wars
has to be the HP-48 series of calculators. They'll run almost
anything. And if they can't, while I'll just plug a Linux box into
the serial port and load up the HP-48 VT-100 emulator.
-- Jeff Dege, jd...@winternet.com
http://www.donarmstrong.com http://rzlab.ucr.edu
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100706075214.gw27...@teltox.donarmstrong.com
