On Nov 9, 2005, at 3:12 PM, Koen van der Drift wrote:
I'm not an 'old pro', but what I usually do for a new package is to remove all non-essential packages (eg with FinkCommander). And then start from scratch to compile the package. Then one by one I start to add packages based on the errors I get. Usually foo-dev are BuildDepends, and foo-shlibs are Depends.
I do basically the same thing. It's largely a trial-and-error process, unfortunately. And even then, sometimes you still don't know whether there is some dynamic dependency that you don't know about until it fails at runtime. That's why I try to rely on the upstream documentation as much as possible. Some of them are pretty good about documenting precisely what external packages are needed, even going into detail about optional packages.
Also, I generally try to overestimate in deciding what packages go into Depends. If I see something only looks like it *might* be a dependency, I go ahead and add it. Better to have too many dependencies than too few.
Trevor ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
