An old issue that I just encountered, is that depencencies in the old format "Foo x.y" is interpreted as just "Foo" while it really should be interpreted as "Foo >= x.y" imo. In my case it was the GnuPG recipe that listed "LibAssuan 1.0.2", while I had 1.0.0, which made configure die when it didn't find a version of that library that matched the prerequisite. We still have some hundred recipes in the store, which have the old dependency format and I cannot guess how many of those that are broken because of not using the version given as a lower limit.
For recipes some fuzz with regard to version is ok, so using the version as least possible would probably be better than just removing it. For binary packages that still have their dependencies in the Dependencies file and does not have a BuildInformation file (does such packages still exist) the version should be interpreted as required, i.e. '='. -- /Jonas -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
