On 2012-05-29 19:50, Tomasz Rybak wrote:
> 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})
That sound a bit like overkill (and may make the job harder for apt).
Package: python-pyopencl-headers
Replaces: python-pyopencl (<< 2011.2+git20120508-1)
Breaks: python-pyopencl (<< 2011.2+git20120508-1)
Should be sufficient to take care of the package split
> for python-pyopencl-headers and
>
> Depends: python-pyopencl-headers (= ${source:Version})
>
> for both python-pyopencl and python3-pyopencl
This will take care that you can't mix the versions badly.
> *-headers Replaces hard-coded version (because *-headers was introduced
> in that version)
ack, use breaks/replaces on 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.
that should already be covered by the versioned Depends
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
