Package: imagemagick
Version: 7:6.4.5.4.dfsg1-1

        Hi there,

 I see you renamed imagemagick's -dev packages in experimental for the
 new upstream names of libs, .pc files, config programs and includes.

 I think this is going to be a painful transition if we move the
 packages as is to unstable.  It would make the transition much smoother
 if we provided compatibility libmagick++9-dev and libmagick9-dev
 packages.

 If we do this, we could use this occasion to also keep the
 compatibility binaries in the old package names to allow to get rid of
 them after the transition.

 These are my notes on the various header, libs, .pc files, and config
 programs:

old                     new                             new
-----------------------------------------------------------
libmagick9-dev          libmagickcore-dev               libmagickwand-dev
-------------------------------------------------------------------------
include/magick/
include/wand/
                        include/ImageMagick/magick
                                                        include/ImageMagick/wand

libMagick.so
libWand.so
                        libMagickCore.so
                                                        libMagickWand.so

Magick-config         D Magick-config
                      R MagickCore-config
Wand-config                                           D Wand-config
                                                      R MagickWand-config

ImageMagick.pc          ImageMagick.pc (D?)
                      N MagickCore.pc (R?)
Wand.pc                                                 Wand.pc (D?)
                                                      N MagickWand.pc (R?)

old                     new
---------------------------
libmagick++9-dev        libmagick++-dev
---------------------------------------

include/Magick++*
                        include/ImageMagick/Magick++*

libMagick++.so          libMagick++.so

Magick++-config         Magick++-config

ImageMagick++.pc        ImageMagick++.pc (D?)
                      N Magick++.pc (R?)

 N: NEW, D: DEPRECATED, R: REPLACEMENT


 I don't think we need to care about libs and headers, as .pc files
 should be used or in the worst case -config programs.  Therefore, I
 think it would make sense to:
 - readd libmagick++9-dev, deping on libmagick++-dev
 - move ImageMagick++.pc to libmagick++9-dev (not clear whether
   ImageMagick++.pc is truly deprecated)
 - readd libmagick9-dev, deping on libmagickcore-dev and
   libmagickwand-dev
 - move Wand-config, Magick-config, Wand.pc, ImageMagick.pc to
   libmagick9-dev (not sure whether the .pc files are truly deprecated)
 - change the Conflicts on libmagick9-dev and libmagick++9-dev to
   Replaces with << first version where libmagick++-dev,
   libmagickcore-dev, and libmagickwand-dev were introduced
 - add Replaces to libmagick++9-dev and libmagick9-dev on
   libmagickcore-dev, libmagickwand-dev, libmagick++-dev << version of
   this change

 What do you think?

   Bye
-- 
Loïc Minier



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to