Hello Michal! Thank you for your response. The think is, that sqlmap per se is a python based software which can simply be executed and is therefore packaged in a noarch file. The tools tries to inject some user defined functions into a target server ( see https://github.com/sqlmapproject/udfhack ). On the server which runs sqlmap, I need to have different libraries for different postgres and mysql versions and for different architectures which is used on the target server that does _not have a sqlmap installation. So for the sqlmap-installation the shared objects are not more than a data-file... Johannes Am 15.01.2013 15:16, schrieb Michal Vyskocil:
Hi Johannes,
this is a big missunderstanding. If package installs architecture dependent files (assuming all .so files are shared objects, and not something else), then it it not noarch package.
As far I can see, all you did is that you have unpacked the binaries from a tarball, which is not how packages are normally done. The normal approach is build everything from source - if nothing it gives you an ability to change things (like where so files will be installed and from where will be loaded).
So the reasonable approach is to
1.) remove all .so files from a tarball 2.) build them in %build phase - this implies BuildArch: noarch removal 3.) install them to %{_libdir}/... 4.) change the code to look for them in a %{_libdir}
Regards Michal Vyskocil
-- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org