On 3/18/02 11:03, "Chris Devers" <[EMAIL PROTECTED]> wrote:
<snip> > Also note that, in my experience, using dselect has been less than > stellar, for reasons a lot like the ones you describe. If you use fink in > the "standard" way -- "sudo fink install dia" for example -- then it does > go out and get the needed dependencies; dselect on the other hand has been > buggy for me, not finding packages, not finding dependencies, etc. On the > other hand, this isn't all that different from when I tried it on Debian > recently, so I'm not ready to blame the Fink folks for that yet. It's a > pain having to build *everything*, but it seems like the binary install > methods currently available just aren't on par with source installations. > Somebody correct me if I'm wrong, but I think that the binary installation uses a different scheme to track its dependencies than does the installation from source. It seems that updates to the binary distribution happen on a much slower timescale than those to the source distro. In any case, if a package has a hidden dependency problem (you can install it, but then you get complaints when you run something from the package) you should directly email the package maintainer, whose email address you can find by doing 'fink describe <package>', where <packagae> is the name of the package you are having problems with. -- Alexander K. Hansen Associate Research Scientist, Columbia University, LDX Collaboration MIT Plasma Science and Fusion Center, 175 Albany Street, NW17-219 Cambridge, MA 02139-4213 Phone: 617-252-1818 Fax: 208-988-4057 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
