Bug 147946 - beagle rpm has explicit libexif dependency
Summary: beagle rpm has explicit libexif dependency
Status: RESOLVED DUPLICATE of bug 198377
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-03 11:11 UTC by Dirk Mueller
Modified: 2006-09-30 04:48 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Mueller 2006-02-03 11:11:06 UTC 
beagle rpm has explicit libexif dependency, while it should use the normal rpm dependency mechanism, which also requires libexif in the correct .so version.
Comment 1 Gary Ekker 2006-02-03 17:34:38 UTC 
libexif is only accessed by managed code, not linked to in the normal fashion.

Wade, Joe do either of you know if there is a way to get RPM to pull in the dependency automatically when the library is listed in a .dll.config file?
Comment 2 Joe Shaw 2006-02-03 18:06:07 UTC 
There's no way to do it right now, the RPM provides/requires scripts for mono only looks at the explicit mono assembly references within .dll and .exe files.
Comment 3 Dirk Mueller 2006-02-03 18:10:30 UTC 
okay, but thats not relevant for discussion. it should require the version it was build against, with other words run

Requires: %( rpm -q --provides libexif | head -n 1 )

in your spec file
Comment 4 Wade Berrier 2006-02-03 18:50:52 UTC 
I guess I don't understand why it matters between depending on an rpm package, or the file in the rpm..

But, on a side note... this would be wonderful if we could pull DllImport deps off, but I don't know of a good easy way to do so.

1. .config files are optional
2. the runtime probes with several methods to find a library name and path on "DllImport"

Getting the DllImport (pinvoke) section from the assemblies isn't hard, but we'd have to go through the same methods as the runtime to map that to a filename.  Maybe this could be done with a program calling into libmono... ?

I'm also not sure it's a good idea since it's a dynamic dep (although mostly static for our purposes with rpms).

Ben, you writing the mono-find-provides/requires... do you have a comment?
Comment 5 JP Rosevear 2006-09-30 04:48:47 UTC 
Believe this is a duplicate now.

*** This bug has been marked as a duplicate of bug 198377 ***