[avrdude-dev] Re: per-user config file - .avrduderc

[eric]

Brian Dean wrote:

> > Still, I'm not totally convinced that overriding the system file is
> > completely necessary. I can see specifying with -C a different config file
> > that is used instead of the system config. I don't see that many users
> > will be customizing or needing to customize the system file except in the
> > very beginning until all the AVR processors are specified in the config
> > file. There's just not that many people making custom programmers that
> > need to override the system.
>
> I think the main reason someone would want to do that is to change the
> defaults.  I.e., list their programmer as the 'default_programmer'.
> Most folks may only have this one single line in their customized
> file.  Doing this will keep them from having to specify their
> programmer on the command line each time they run avrdude, so if
> there's a way you can provide that, I think it could be useful.
>

Now I got it. My guess then is that the user config file will be in the same
directory as the binary and the system config file. The only real issue would be
the user config file name. Something like .avrduderc is not that common on
Windows (i.e. starting off with a dot and a long "extension"). Perhaps the name
will change for Windows.

>
> > BTW, once avrdude is distributed with WinAVR on Windows, it's user base
> > will increase dramatically. In just over 5 weeks, WinAVR 20030115 has
> > gotten over 7,000 downloads. :-)
>
> Yikes - I better get my e-mail address out of the binary, perhaps
> replace it with code to plant a subliminal suggestion that they
> purchase one of my boards from www.bdmicro.com :-)
>

Hey go for it! I figure since you opened up your project to allow porting and
such you can plug your stuff as much as you want!

FYI, I'm currently considering releasing the next WinAVR during the second week
in March. Hopefully that will be enough time to resolve the few remaining issues
here. Which are?.... What, the configuration file, some auto tools stuff, and
documentation. I think that's about it that's needed for a good initial release.

Eric