Danek Duvall wrote: > On Tue, Jun 10, 2008 at 04:10:31PM +0800, Dave Lin wrote: > > >> I set up an IPS repos. locally. But I found the pkg SUNWgnome-file-mgr >> missed the dependency on SUNWgnome-gvfs when I converted the svr4 pkg >> into the IPS repos. So I'd like to know how does IPS calculate the >> dependencies, is there something wrong? >> > > Is this different from SUNWgnome-vfs? > Yes, they're totally different pkgs. > At any rate, solaris.py only determines dependencies based on what's in an > ELF object's DT_NEEDED section; i.e., a library that it's been directly > linked against. Plugins that are only ever referenced via dlopen() can't > be found programmatically, so you'll have to add the dependency by hand. > I see, that's the reason. I copy & paste Ghee's clarification and question from another thread.
****************** Let me rephrase the problem: SUNWgnome-gfvs is new in gnome 2.22, its is required by a number of apps such as nautilus, evince etc. But the dependency is not through conventional linking of libraries. There is a daemon serving the request of client such as nautilus and then the daemon invoke some binaries. Hence, there is no build time dependency nor run-time implicit dependency. So when one upgrade pkgs from gnome 2.20 to 2.22, the SUNWgnome-gvfs is not installed using ips. How can we ensure that SUNWgnome-gvfs is loaded when package like SUNWgnome-file-manager is upgraded to 2.22 ? The generic case of the problem would be how do we ensure new packages are installed without dependency on existing packages? ****************** Dave _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
