Bugs item #1206, was opened at 2009-11-24 21:52
Status: Open
Priority: 3
Submitted By: Stephan Kleine (bitshuffler)
Assigned to: Nobody (None)
Summary: [openvas-administrator] Installation directories are wrong.
Architecture: None
Resolution: None
Severity: None
Version: None
Component: None
Operating System: None
Product: None
Hardware: None
URL:
Initial Comment:
on Fedora cmake -DCMAKE_INSTALL_PREFIX=%{buildroot}%{_prefix} . results in:
/usr/bin/openvasad
/usr/etc/openvas/openvasad_log.conf
cmake -DCMAKE_INSTALL_PREFIX=%{buildroot} . in:
/bin/openvasad
/etc/openvas/openvasad_log.conf
and after applying the attached patch (which I'm _not_ sure is the proper
solution) it works in Fedora with cmake -DCMAKE_INSTALL_PREFIX=%{buildroot} .
but then stuff gets installed into
/var/tmp/openvas-administrator-0.2.2-build/etc/openvas/openvasad_log.conf
/var/tmp/openvas-administrator-0.2.2-build/usr/bin/openvasad
(as in it gets installed into %{buildroot}/%{buildroot}/... ).
What I need is a simply way to tell it to install itself bellow %{buildroot} in
the same layout it then needs to be bellow / once installed.
Also review the includedir path in the CMakeList since it should be
/usr/include, not /include.
Further the libdir path is hardcoded to /usr/lib which shouldn't happen either
since most put 64 bit libs into /usr/lib64
E.g. normally stuff is defined like the following:
%_prefix /usr
%_exec_prefix %{_prefix}
%_bindir %{_exec_prefix}/bin
%_sbindir %{_exec_prefix}/sbin
%_libexecdir %{_exec_prefix}/libexec
%_datadir %{_prefix}/share
%_sysconfdir /etc
%_sharedstatedir %{_prefix}/com
%_localstatedir %{_prefix}/var
%_lib lib
%_libdir %{_exec_prefix}/%{_lib}
%_includedir %{_prefix}/include
%_infodir %{_datadir}/info
%_mandir %{_datadir}/man
(on x86_64 %_lib is overridden to lib64) which is prolly how you should define
your directories as well (albeight I'm a bit surprised that this is necessary
with cmake. Are you sure there isn't a more "natural" way to do it?)
----------------------------------------------------------------------
You can respond by visiting:
http://wald.intevation.org/tracker/?func=detail&atid=220&aid=1206&group_id=29
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
