Bug 919732

Summary:	cups-config should be moved to -devel package
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Dominique Leuenberger <dimstar>
Component:	Printing	Assignee:	Johannes Meixner <jsmeix>
Status:	RESOLVED DUPLICATE	QA Contact:	Johannes Meixner <jsmeix>
Severity:	Normal
Priority:	P5 - None
Version:	201502*
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Dominique Leuenberger 2015-02-26 14:18:56 UTC

cups-config is wrongly installed as part of cups-libs, when it's actually only used for development purposes.

it is NOT there to configure cups, but rather to give linker/compiler hints to other programs (similar to pkg-config)

Comment 1 Johannes Meixner 2015-02-26 14:39:38 UTC

cups-config is totally intentionally part of cups-libs.

It is NOT (why did you write 'NOT' and not 'not'?) ONLY
there for build-time software like linker/compiler.

For example any software might run "cups-config --version"
during runtime.

As far as I rememeber off the top of my head it is in cups-libs
because it is also needed by some other software during runtime
and cups-libs is the only CUPS binary RPM that is installed
in any case - even in a build system and also in a minimal system
that somehow likes to use CUPS at least in some minimalist way.

Right now I don't know the details - it was long before I became
CUPS maintainer - I just did the usual and had a look at the
cups.changes package source file and I found:
-------------------------------------------------------------------
Sat Jan 14 17:50:52 CET 2006 - lmuelle@suse.de

- Move cups-config to the libs sub package. Then we do not bother
  anyone as cups-libs is required by cups-devel and cups; [#142004].

...

Wed Jan 11 19:03:06 CET 2006 - kssingvo@suse.de

- moved cups-config into main package (bugzilla#142004)

-------------------------------------------------------------------
For details see
https://bugzilla.opensuse.org/show_bug.cgi?id=142004

Hey!
This issue was even reported by me!

*** This bug has been marked as a duplicate of bug 142004 ***