[Bug 225804] Merge Review: glib2

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Merge Review: glib2


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225804





------- Additional Comments From rc040203 at freenet.de  2007-02-06 06:03 EST -------
(In reply to comment #14)
> (In reply to comment #13)

> Considering the discussions on bug 225875 (see comments by Patrice Dumas and
> Ralf Corsepius), please either own the directory or depend on something that
> does. I believe this is mostly to make sure that installing the package and then
> removing it doesn't leave empty directories around.
You are right on the spot - This is what this is all about.
 
> All other blockers are fixed now. The package is fine
In addition to what has already been said: When building the fc7/devel glib2
package on fc6, the test-suite hangs.

> Final rpmlint output:
> W: glib2 non-conffile-in-etc /etc/profile.d/glib2.sh
> W: glib2 non-conffile-in-etc /etc/profile.d/glib2.csh
These are OK.

> E: glib2-devel only-non-binary-in-usr-lib
> E: glib2-static devel-dependency glib2-devel
> W: glib2-static no-documentation
> W: glib2-static devel-file-in-non-devel-package /lib/libglib-2.0.a
> W: glib2-static devel-file-in-non-devel-package /lib/libgobject-2.0.a
> W: glib2-static devel-file-in-non-devel-package /lib/libgthread-2.0.a
> W: glib2-static devel-file-in-non-devel-package /lib/libgmodule-2.0.a

These are not fine. glib2 can install its runtime libs into /lib if it needs to,
but installing devel-libs there is NOT OK.

Matthias, please check how glibc is being packaged. They install the
runtime-parts into /lib and install the devel parts to %{_libdir}
(Technically this should not be much more than an ordinary %configure plus
moving the lib*.so.* in %install)


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.