On Tue, 22 Sep 2015, László Böszörményi wrote:
On Tue, Sep 22, 2015 at 7:17 PM, Jakub Wilk <jw...@debian.org> wrote:
* László Böszörményi (GCS) <g...@debian.org>, 2015-09-22, 08:25:
[2] dget -x http://www.barcikacomp.hu/gcs/graphicsmagick_1.3.21-4.dsc
You changed the package name, but not the SONAME. That doesn't sound right.
Yes, I know that. Still the packages can be tracked during a
transition via the package name if those were compiled against the
quantum-depth change or not. I have to change the package name anyway,
I can't just change the SONAME. Then I don't see the mandatory to
change the SONAME, the package name change will make it distinct of
the quantum-depth difference.
If there are two packages with different quantum depth, then they
should be able to co-exist without conflict. Likewise, the existing
package should be able to co-exist with new packages which are
distinguished via quantum depth so that existing software continues to
work.
Dependent applications should be re-compiled and re-linked against the
new packages so they stop using the old library.
A factor to consider is that GraphicsMagick packages of the same
GraphicsMagick release version and quantum depth will share coder and
filter modules which are under a path like
/usr/lib/GraphicsMagick-1.3.21/modules-Q16. Changing to the new
scheme without also transitioning to a new version will result in
over-writing existing coder/filter modules and these will now
reference the new GraphicsMagick library rather than the old one.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
