Bug 3518 - oxygen-gtk3 is not properly libified
Summary: oxygen-gtk3 is not properly libified
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Juan Luis Baptiste
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-28 11:47 CET by Colin Guthrie
Modified: 2011-12-13 23:16 CET (History)
1 user (show)

See Also:
Source RPM: oxygen-gtk3
CVE:
Status comment:


Attachments

Description Colin Guthrie 2011-11-28 11:47:50 CET
oxygen-gtk3 is not properly libified which prevents installing it and expecting the theme engine to work for 32 and 64 bit apps at the same time.
Comment 1 Juan Luis Baptiste 2011-11-28 17:48:00 CET
Ok, tell me what to do because I don't have a clue of what would be to "libify" a package. Or do you mean to split the package on oxygen-gtk3, liboxygen-gtk3 and liboxygen-gtk3-devel ?

CC: (none) => juan.baptiste
Assignee: bugsquad => juan.baptiste

Comment 2 Colin Guthrie 2011-11-28 17:57:56 CET
Awesome! I've replied on list.

In order to make upgrades smooth, you'll have to add "Conflicts" to the new sub-packages you create that will include:

Conflicts: oxygen-gtk3 < %{version}-%{release}

You can technically expand the version and release macro here to fixed values as future versions will not need to conflict.

The only reason the conflicts are there is that you'll need to add some requires in the sub-packages to require back the common data!

Have a look at how it's done in oxygen-gtk and if in doubt just ask (preferably on IRC!)
Comment 3 Juan Luis Baptiste 2011-11-28 21:56:59 CET
Ok I have "libified" and pushed the package as collin suggested. Please test and post results.
Comment 4 Juan Luis Baptiste 2011-12-13 22:59:29 CET
Colling, did you reviewed the package ?
Comment 5 Colin Guthrie 2011-12-13 23:16:14 CET
Oh yes, sorry I forgot to update this bug... bad me :)

Looks good to me :) Many thanks!

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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