Hello Shuan!

I guess these two new lines should go to "%files clients" section instead  
of main openhpi package section.

The rationale:

main openhpi package contains openhpi daemon
man1/* contains manual pages for hpi clients
openhpiclient.conf - configuration file for HPI client library.

        Anton Pak


On Thu, 26 Feb 2009 19:08:27 +0300, Shuah Khan <[email protected]> wrote:

> All,
>
> Please review the following svn diff and give me feedback. If I don't
> hear any objections, I plan to commit the change by end of day today.
> Thanks in advance for a quick review.
>
> This patch adds new man pages and openhpiclient.conf to the package list
> for rpm build. These new files got added to the trunk back in 2.13.1
> with addition of multiple domains feature and didn't get added to the
> spec file for packaging, as a result we are seeing rpm build failures.
>
> svn diff openhpi.spec.in
> Index: openhpi.spec.in
> ===================================================================
> --- openhpi.spec.in     (revision 6963)
> +++ openhpi.spec.in     (working copy)
> @@ -223,10 +223,12 @@
>  %dir /var/lib/%{name}
>  %{_libdir}/libopenhpi*.so.*
>  %{_libdir}/liboh*connx*.so.*
> +%{_mandir}/man1/*.1*
>  %{_mandir}/man7/%{name}.7*
>  %{_mandir}/man8/%{name}d.8*
>  %{_sbindir}/openhpid
>  %{_sysconfdir}/init.d/openhpid
> +%{_sysconfdir}/openhpi/openhpiclient.conf
> ###################################################
>  %files devel
>
>
> Thanks,
> -- Shuah



------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to