Philip Lamb wrote: > Hi all, > > I have a package I'm updating that depends on libgnome2 and libgnomeui2. > When I run otool -L on the built binary, I see all the inherited gnome > shared libraries. > > My question is, do I have to list every shared library from libgnome2 > and libgnome2ui as a dependency of my package, or is it enough to have a > depends: libgnome2-shlibs, libgnome2ui-shlibs and let the inherited > depends be installed that way?
Technically speaking, you don't need to include the inherited dependencies. It's more a question of clarity and ease of maintenance. If you depend on indirect dependencies, your package can be broken by an update of libgnomeui2-shlibs, for example, on which you have no influence. Unless you Depend on a precise version of libgnomeui2-shlibs, which you usually don't want to, you would even have to make sure that there aren't other versions of that package around that lack some of your needed dependencies. Concerning BuildDepends, the inclusion of inherited dependencies is mandatory, as long as Fink's InheritedBuildDepends mechanism is still in the state of a nice dream. -- Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
