Rafael Laboissiere <[email protected]> writes: > Sure, I have overseen this. I will fix it tonight.
Thanks! > At any rate, I do not understand why you suggest to depend on both gcc and > gcc-4.3. Would the following be okay? > > gcc (>= 4:4.3.3), gcc (<< 4:4.3.4) No, because gcc's dependency on gcc-x.y merely specifies a lower bound; when a new upstream version comes along, gcc-defaults can lag for weeks until there's a reason to force a higher subminor version, and even then the dependencies continue to allow for even newer upstream versions. As such, you merely need a gcc package that depends on the appropriate gcc-x.y package, but you must additionally specify tight dependencies on the latter. > Unfortunately we need to depend on a precise version (4.3.3 currently > because paths containing this version number is hard-coded in mkoctave. So I gather; it would be great if you could somehow fix that. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
