Martin Schulze <[EMAIL PROTECTED]> writes: > I'd suggest that all such packages only try to compile and package the > libc5 packages if there is a libc5 installed.
No, that's a bad idea. A package might silently build incorrectly because a developer didn't have libc5 or libc5-dev installed. Unfortunately hard-coding the architectures which do (or don't) have libc5 isn't very aesthetic. Does anybody have a better idea? Guy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
