Dnia 2012-05-29, wto o godzinie 11:33 +0200, Andreas Beckmann pisze:
> On 2012-05-27 21:06, Tomasz Rybak wrote:
> > Should I put
> > Breaks/Replaces: python-pyopencl (<< 2011.2.2+git20120508-1)
> > or
> > Breaks/Replaces: python-pyopencl (<< ${source:Version})?
> > Policy 7.6 uses hard-coded version, but many packages put
> > ${source:Version} into debian/control. What is advised?
>
> A hardcoded version would be advised because there was a change once in
> the past, but any version afterwards is not affected by this.
>
> source:Version is used for other purposes (usually for Relationships
> with arch:all packages that don't have a matching binary:Version (at
> least after an NMU).
Thanks for the explanation.
I have decided to put:
Replaces: python-pyopencl (<< 2011.2+git20120508-1)
Breaks: python-pyopencl (<< ${source:Version}),
python-pyopencl (>> ${source:Version}),
python3-pyopencl (<< ${source:Version}),
python3-pyopencl (>> ${source:Version})
for python-pyopencl-headers and
Depends: python-pyopencl-headers (= ${source:Version})
for both python-pyopencl and python3-pyopencl
*-headers Replaces hard-coded version (because *-headers was introduced
in that version) and Breaks Python modules in all versions not equal
to itself because those modules include headers during compilation,
which might mean that compiler needs headers from its version.
Regards
--
Tomasz Rybak GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860
http://member.acm.org/~tomaszrybak
signature.asc
Description: This is a digitally signed message part
