Ben Hines <[EMAIL PROTECTED]> wrote: > Do you have a script that will let us determine all the builddepends > we should be putting in our packages? (ie, all the ones you have been > adding to people's info files. :) > > -Ben
Hi Ben. I'm answering to the fink-devel list because other people may want to know the same thing. If you have a new package, here's what you should do to test (now and in the future). Check your dependencies to make sure they are not BuildDependsOnly, and if they are, replace them with the -shlibs version or whatever is appropriate in your package. Now, try building your package with the main or -dev versions of those packages *not* installed. Does it still work? Now I have to admit that this can be difficult at present, because lots of BuildDependsOnly=True packages actually do have things depending on them, so they are hard to remove. So the "safe" alternative, which is what my script does, is to find all dependencies of dependencies of dependencies, and add the main or -dev versions of those packages to the BuildDepends of the present package. I'll try to find the time to put a list of all of the BuildDependsOnly=True packages and which version (main or -dev) you should put into the BuildDepends field of you package, up on the website or CVS somewhere. -- Dave _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
