[Bug 603514] Review Request: libmodman - A simple library for managing C++ modules (plug-ins)

[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.


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

--- Comment #20 from Chen Lei <supercyper1 at gmail.com> 2010-06-19 22:53:56 EDT ---
(In reply to comment #19)
> My goal with libmodman and F-13 is to get libmodman working in F-14 with
> libproxy >= 0.4.4, then I will backport to F-13 and remove the conflicts.  That
> is why I applied for a libmodman F-13 branch.
> 
It make sense, I can't find any better solution right now :)

> So the only outstanding issue I can see is the libmodman-devel directory
> ownership issue.  I believe this can be resolved by having libmodman-devel
> require cmake (which owns the directory).  If this is not appropriate, please
> suggest an alternative option.    

Requires cmake if building libproxy 0.4.4 need this file or simply remove this
file after make install.

For pkgconfig, see
http://fedoraproject.org/wiki/PackagingGuidelines#Pkgconfig_Files, but requires
pkgconfig is also Okay, it's the same.

Incluing documentions in -devel is not mandatory, some rpmlint warnings can be
ignored, e.g. W: spelling-error, W: no-documentation. You don't need to add
LICENSE file to all subpackages, -devel subpackage should only contain docs
which are related to development e.g. apidocs.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.