Re: [avrdude-dev] RE: avrdude-dev Digest, Vol 13, Issue 1

[Jan-Hinnerk Reichert]

On Thursday 05 February 2004 08:25, address@hidden wrote:

> For what it's worth, I tested the binary avrdudew32_20040204.zip
> ("avrdudew32 Version 0.3 for CYGWIN build environment") with the
> futurlec board under Win2k and it worked perfectly. Actually, it
> was surprisingly fast, so at first I thought it crapped out. But
> no, it did what it had to do, just quicker than I expected.
>
> Guys, since my addition to avrdude.conf didn't make it to the 4.3.0
> build, would you object if I made available the modified
> avrdude.conf file on my website?

My main concern is generating confusion among the users. You should 
also wait if one of the elders (SCNR) has something to say about it.

IMHO, we have no right to forbid you publishing something, as long as 
you comply with the GPL. However, we might be angry with you, if it 
turns out badly...

----------

Here's my two cents:

Safest way is to redirect visitors to the CVS-archive. You can also 
access the CVS over a webinterface. The link below is a page with all 
versions of "avrdude.conf.in".
http://savannah.nongnu.org/cgi-bin/viewcvs/avrdude/avrdude/avrdude.conf.in

The next one is a download link for the current version of this file:
http://savannah.nongnu.org/cgi-bin/viewcvs/*checkout*/avrdude/avrdude/avrdude.conf.in?rev=HEAD&content-type=text/plain

----------

If you think this is too complicated for your visitors, you should at 
least mention that "futurlec"-support is added in CVS and will appear 
in the next release.

I also suggest that you don't publish the whole "avrdude.conf", but 
only the futurlec-definition and/or a .diff there. If you make a diff 
make sure you include "4.3.0" somewhere in the file name. Saves a lot 
of space and traffic, too.

Cheers
  Jan-Hinnerk