Do packages with loose dependencies need to explicitly say "I require
either gdbm OR gdbm3", openmotif3 OR lesstif, etc.?
On Jun 26, 2005, at 2:10 PM, Daniel Macks wrote:
It's against Fink policy to say "either gdbm or gdbm3" because doing
so often gives functionally-broken binaries, or else often would
require massively larger dependency trees than we already have. One
can specify alternatives among packages that are drop-in replacementsw
for each other (python23|python23-nox, db43-ssl|db43), but different
numbers in the package-name indicate that the packages are *not*
binary-compatible.
I understand, but then if packages are not binary compatible, why does
fink uninstall one for the other, e.g.:
Selecting previously deselected package db3.
dpkg: considering removing db43-ssl in favour of db3 ...
dpkg: yes, will remove db43-ssl in favour of db3.
Fink is acting like I can't have both, but apparently my set of
installed programs do require both.
Others have suggested that I just "keep doing fink update-all until it
finally completes", but it sounds as if I have an incompatible set of
programs I'm trying to update.
Thanks for elucidation. (I've looked at the Fink FAQ TOC and don't see
anything about dependencies and versions.)
--
=S
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
