Bug 64249 - Magick*-config should be in devel package
Summary: Magick*-config should be in devel package
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: ImageMagick   
(Show other bugs)
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: wdovlrrw
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 67217
TreeView+ depends on / blocked
 
Reported: 2002-04-30 16:43 UTC by Moritz Barsnick
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-06-21 04:48:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Moritz Barsnick 2002-04-30 16:43:47 UTC 
Description of Problem:

In ImageMagick's base package, /usr/X11R6/bin/Magick-config and /usr/X11R6/bin/Magick++-config are delivered. IMHO, this is a bit misleading, as they are only really good for _developing_ something with ImageMagick. They should therefore be in ImageMagick-devel.

A side effect is that programs using libMagick may try to compile with Magick-config's output info, but fail due to missing installment of ImageMagick-devel.

Version-Release number of selected component (if applicable):

5.4.3.11-1

How Reproducible:

always

Steps to Reproduce:
1. try to build an app which relies on the ImageMagick libs (i.e. on ImageMagick-devel), such as autotrace.
2. 
3. 

Actual Results:

./configure finds Magick-config, and possibly relies on its result (e.g. "Magick-config --cflags" or "Magick-config --libs").

Expected Results:

Build should fail due to missing Magick-config, not to missing (but expected) header files or libs.

Additional Information:
Note You need to log in before you can comment on or make changes to this bug.