On 01/11/2016 11:48 PM, Orion Poplawski wrote:
> The julia language loads libraries at run time by using the .so filename. We
> work around this in the julia package by symlinking the needed sonames into
> %{_libdir}/julia/, e.g.:
>
> for lib in arpack cholmod dSFMT git2 fftw3_threads gmp mprf openlibm
> openspecfun pcr2-8 umfpack
> do
> soname=$(objdump -p %{_libdir}/lib${lib}.so | awk '$1 == "SONAME" { print $2}')
> ln -s ../${soname} %{buildroot}%{_libdir}/julia/lib${lib}.so
> done
>
> Now we want to automatically generate the needed rpm requires, e.g.:
>
> libarpack.so.2()(64bit)
>
> What I came up with is a rpm-julia-hooks package that julia would BR that
> would use rpm fileattrs to generate these. This feels a bit klunky having a
> separate package just to do this task.
>
> Does anyone else have any ideas?
Looks like you are trying to use a custom dependency generator in
addition to internal one. If it's for use in a single package then the
following solution should work:
%global _use_internal_dependency_generator 0
%global __find_requires %{SOURCE666} %{_rpmconfigdir}/find-requires
Source666: %{name}-find-requires.sh
Where julia-find-requires.sh should be a script that generates custom
requires (prints them to stdout) and then calls internal RPM dependency
generator (passed as $1).
--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
