Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
Summary: Review Request: avrdude -Software for programming Atmel AVR Microcontroller
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=230324
------- Additional Comments From rc040203@freenet.de 2007-02-28 08:26 EST ------- [Another mid-air collision ;)]
(In reply to comment #5)
(In reply to comment #3)
(In reply to comment #1)
- What also makes me wonder is the sources shipping a *.info but the package not
installing it ?!?
It is, good catch.
The appropriate automake-magic is in doc/Makefile.am, but it's commented out, for reasons I can only guess on - Is upstream still active? Then they might want to clean up their sources ;)
(In reply to comment #2)
- Can you explain a bit about how the config file is not supposed to
be modified by end-users?
I doubt Trond's statement. It's a system-wide configuration file, being generated by the configure script, not a sample. IMO, if it's a sample then it must not be located under /etc but should be placed elsewhere (e.g. %doc)
For the moment I'd recommend to use %configure ... --sysconfdir=%{_sysconfdir}/avrdude And to mark it %config(noreplace)
i.e. to treat it as a system-wide config file.
Agreed, but why put it in a seperate subdir of /etc,
why not?
do we expect avrdude to have multiple config files, is there a guideline for this I'm not aware of.
Nope, it' just my personal preference. For two reasons:
1. I hate package polluting /etc and I hate packages which momentary (temporarily?) apply one single configuration file, because packages in longer terms tend to have more than one config file.
2. In case of embedded tools, I tend to have several config files reflecting different setups, which I tend to keep in parallel. I don't use avrdude, so I am not sure if this applies in this particular case. Probably most users will apply setups in ~/ should they need customized setups.