I'm passing on a request from one of our users (made in correspsondence about a bug he reported). He uses dselect, and tried to install some things which are available as binaries, but they depend on other things which are not available as binaries. Is there any way we can add something to dselect to communicate this fact to the user? Or should we be drastic and only distribute binaries when all of the dependencies are also available as binaries?
-- Dave Here's his comment: > Ok, then can you add such a comment in the dselect > package descriptions -- I got stuck in the dependency > sub-menus for quite some time because tetex-base > requres tetex-texmf and tetex-system provides tetex- > texmf, but tetex-base conflicts with tetex-system. And > the result is that dselect won't install anything having to > do with tetex. _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
