Bug 88373 - Packaging bug: libgnome-window-settings.so not included
Packaging bug: libgnome-window-settings.so not included
Status: CLOSED DUPLICATE of bug 88375
Product: Red Hat Linux
Classification: Retired
Component: control-center (Show other bugs)
9
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Blandford
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-09 11:20 EDT by Andrew Sobala
Modified: 2013-04-02 00:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:52:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Sobala 2003-04-09 11:20:19 EDT
control-center includes these files:

libgnome-window-settings.so.1
libgnome-window-settings.so.1.0.0

It is missing:

libgnome-window-settings.so

So applications work, but ld refuses to link any new packages against this library.
Comment 1 Alexander Larsson 2003-08-29 06:39:02 EDT
The specfile specifically removes the .so file. Probably because nothing should link against this library (it has no headers for instance).

What tried to link against it?
Comment 2 Andrew Sobala 2003-08-29 07:43:53 EDT
This was from when themus was a standalone module; it needed this to change
window themes.

I'm going from memory here, but I think the relevant headers are installed by
the control-center tarball in include/gnome-window-settings-2.0/*.h. So if the
headers aren't meant to be installed then that's an upstream bug.
Comment 3 Marco Pesenti Gritti 2004-10-21 07:36:28 EDT
Marking this as a dup of 88375 and adding a comment there. These needs
to be fixed together.

*** This bug has been marked as a duplicate of 88375 ***
Comment 4 Red Hat Bugzilla 2006-02-21 13:52:35 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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