On Sat, Jan 19, 2008 at 05:32:13PM +0100, Raphael Hertzog wrote: > BTW, I noticed two other potential problems: > [EMAIL PROTECTED] 1:1.1.2 > [EMAIL PROTECTED] 1:1.1.4
> Why do the minimal version not match the version of the symbol ? The symbol versioning was added retrospectively upstream. I'll have to check back but ISTR that some of the symbols were attached to the wrong versions. It doesn't really make any difference since there was no versioning in the older versions anyway. I've got a feeling adler32_combine is a tyop, though. > But maybe we can have a lintian warning if the name of the package appears > nowhere in the dependency. That would probably be a good idea. I wonder if the header line could even be autogenerated since I'd expect 90% of packages are going to want to use the same template? > Well, I put important because I thought you overlooked it not because the > problem was really critical. And while I agree the warnings are useful, I Ah, I do tend to take the severity of bug reports as reflecting the severity of the bug. > don't understand why one would want to keep them instead of taking proper > measures to not generate them. :) Like I say, I'm conservative about deviations from upstream - if the problems aren't serious I would rather not deviate from upstream. In this case it shouldn't matter if the symbols are there since nothing ought to be using them in the first place. > shouldn't be used, I'd rather make that explicit than let them generate a > dependency on a recent version of the lib which might go unnoticed. Yes, me too but I didn't see any way to do that. > Maybe we need some standard mechanism for this, I don't know. Initially I > drafted that we could put "-" as version on some symbols to mean that they > are private and shouldn't be used but I never implemented that. Yes, that would be a useful feature to have. Perhaps even allowing some text to explain why the symbol should not be used or otherwise provide a hint to someone who does end up using the symbol. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
