> What about the case where it is the binaries in the package that are > depended upon? > > EG: Some new package might consist of a number of python scripts, thus > pythonN would be be required.
This part of the policy only applies to packages supplying shared libraries. As it says a bit further down, if a package supplies both shared libraries and binaries, then the binaries will need to be separated out into yet a third package. (Of course, if the binaries are things like foo-config which are only used when you are compiling something against foo, this won't be necessary.) So really, in some cases we will need three packages: foo, foo-shlibs, and foo-bin. -- Dave _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
