On Thu, 14 Jun 2007, Klaus Heinz wrote:

> so far, I have never had the need to know exactly what to do in case the
> package I update is a prerequisite for many other packages.
> Unfortunately this happy state is about to end.
> 
> I have an update for graphics/ImageMagick 6.3.4.8 ready (ok by adam@)
> and would like to know how to proceed after committing this to CVS.
> 
> According to fgrep, the following packages rely on ImageMagick by means
> of including buildink3.mk:
> 
>   devel/libextractor
>   graphics/autotrace
>   graphics/dx
>   graphics/kipi-plugins
>   graphics/p5-PerlMagick
>   graphics/pixieplus
>   graphics/x11rec
>   misc/koffice
>   multimedia/dvdauthor
>   multimedia/dvdrip
>   multimedia/xine-lib
>   wip/LabPlot
>   wip/fbida
>   wm/fvwm-themes
>   www/zope25-Photo
> 
> Am I supposed to bump the revision of those packages?

The Pkgsrc Guide says:

	"PKGREVISION must also be incremented when dependencies have ABI 
	changes."

Did the ABI change?

Also see in that Guide about "Updating BUILDLINK_API_DEPENDS.pkg in 
buildlink3.mk files".

What might be confusing above is that some of these may not really use 
ImageMagick's library, but use a standalone tool line "convert". For 
example, maybe graphics/x11rec will have no change (I don't know).

> What about packages who rely on ImageMagick through a simple DEPENDS
> assignment?

I wouldn't worry about them. If some command-line options for some 
ImageMagick tool used become incompatible, then we can look at it further.

  Jeremy C. Reed