[Bug 254209] Review Request: g-wrap - A tool for creating Scheme interfaces to C libraries

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

Summary: Review Request: g-wrap - A tool for creating Scheme interfaces to C libraries


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





------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2007-08-29 03:41 EST -------
(In reply to comment #9)
> > * Please check which package owns %{_libdir}/%{name}/modules/
> >  (currently no package)
> 
> hm...%{_libdir}/%{name} is owned by current main package
  Yes

> that imply its
> subdirectory which's shipped & provided by main package to be owned
> to same one.
  It may be that I don't understand correctly what you want to say, however
  if you write "%dir foo/", the subdirectories of foo/ are not _automatically_
  owned by any subpackages.


> > * I don't know what software calls g-wrap modules, however usually
> >  modules are dlopen'ed with the name '*.so', not '*.so.X'.
> >  So I guess libgw-guile-*.so under %{_libdir}/%{name}/modules/
> >  should be in main package, not in -devel subpackage.
> 
> do you also check this:
> $ file libgw-guile-*.so
> libgw-guile-gw-glib.so:  symbolic link to `libgw-guile-gw-glib.so.0.0.0'
> libgw-guile-standard.so: symbolic link to `libgw-guile-standard.so.0.0.0'
 Symlinks themselves are no problem, the problem is how these modules
 are dlopened (with what name).

-- 
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, or are watching someone who is.