On Tue, Feb 19, 2008 at 03:43:09AM -0600, William Pitcock wrote:
> libprojectM upstream are soon releasing libprojectM 1.1 which makes the
> following breakage:
>
> public: PCM *projectM::pcm
>
> is replaced by:
>
> public: const inline PCM *projectM::pcm() { return _pcm; }
>
> So, is this the proper solution:
>
> * libprojectm1 -> libprojectm2
Yes, though you need to convince upstream of that, rather than acting
solely for Debian.
> * libprojectm-dev -> libprojectm2-dev
> * libprojectm-dev becomes virtual package of libprojectm2-dev
>
> If not, what should I do differently?
As Michal said, you don't need to rename the -dev package, unless you
want to support compilation against old versions of the library. If not,
it continue to use an unversioned name.
If you do want to support compilation of old versions then you need to
rename the source package also, ie have parallel libprojectm1{,dev} and
libprojectm2{,dev} packages.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
