Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes: > On Wed, Mar 15, 2006 at 09:06:38PM -0800, Russ Allbery wrote:
>> The only additional thing that I think would be cool to get into this >> release is the patch attached to the bug log for Bug#344269. [...] > I'll review the commits leading up to this release anyway before the > release is really going to happen, so if you things it'd be good to have > this in now, just go ahead. It's about supporting a very very dirty hack > not needed in Debian, I'd rather simply see it not happen anywhere, but > realisticly, that's not going to happen. > If users end up falling all over us due to this [unlikely], we can > quickly enough roll out a new version :). Okay, I'll see if I can get that committed tomorrow. >> I have an idea on how to solve Bug#344266 in a more thorough fashion, >> but that can wait for the next release. > That'd even be better. I should have noted for clarity that that's a different bug number than the one the rest of my message was about. I only noticed after sending that the bug numbers are very similar. The second bug is another report from Frank, this one about more false positives from the bashisms check. I think the right thing to here is to strip all single-quoted strings from the line before we start doing bashism checks, and strip all double-quoted strings before doing the checks that aren't intentionally triggering on things involving variable interpolation. That should remove from lintian's view a lot of things that could cause false positives, including Frank's example, in a fairly clean fashion. I have to really think about the existing checks and make sure that this doesn't cause us to miss something we currently catch, though, so I won't get that patch written soon. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
