| Summary: | oxygen-gtk3 is not properly libified | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Colin Guthrie <mageia> |
| Component: | RPM Packages | Assignee: | Juan Luis Baptiste <juan.baptiste> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | juan.baptiste |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | oxygen-gtk3 | CVE: | |
| Status comment: | |||
|
Description
Colin Guthrie
2011-11-28 11:47:50 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 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!)
Ok I have "libified" and pushed the package as collin suggested. Please test and post results. Colling, did you reviewed the package ? Oh yes, sorry I forgot to update this bug... bad me :) Looks good to me :) Many thanks! Status:
NEW =>
RESOLVED |