RE: [avr-gcc-list] no avr/lib/avr25/attiny13a/Makefile.in

[Weddington, Eric]

> -----Original Message-----
> From: Ruud Vlaming [mailto:address@hidden 
> Sent: Thursday, January 29, 2009 8:39 AM
> To: Weddington, Eric
> Cc: address@hidden
> Subject: Re: [avr-gcc-list] no avr/lib/avr25/attiny13a/Makefile.in
> 
> On Thursday 29 January 2009 05:54, you wrote:
> 
> > Yes, the version checking in the bootstrap script is 
> > quite stupid. Right now it looks for specific versions only.
> > It would be ideal if we could look for a range.  
> > 
> > > The question is: is this really needed? Can the
> > > script not simply issue a warning and go on?
> > 
> > I'm certainly open to changing it. Can you provide a patch?
> 
> Yes, but first we have to decide, what should the patch do?
> Imho that patch should not block execution at all, only warn
> for a possile mismatch of version numbers.
> 
> The point is, until we have a firm spec how all applications
> should emit their version nummers over de command line,
> there will not be a stable solution for version number 
> comparison. 
> 
> I have written a script which does a reasonable job for in most
> situations for version numbers up to three level version numbers.
> However, this is quite lengthy, and still is not bullitproof.
> I think this is not adequate for this situation.
> 
> If you agree with me that a simple version comparison with a
> two digit number, emmiting a warning only is sufficient in this
> case i can make the patch.

I'm ok with say that we require some verion >= X. Anything < X should fail. 
Anything >= X should be allowed. With X being the lowest version that we check 
for.